Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
6994ac85
Commit
6994ac85
authored
May 22, 2002
by
Bruce Korb
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
describe how to fix up the results after adding/changing an inclhack.
From-SVN: r53719
parent
c7539aa0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
0 deletions
+11
-0
gcc/fixinc/README
+11
-0
No files found.
gcc/fixinc/README
View file @
6994ac85
...
...
@@ -34,6 +34,17 @@ definitions file, ``inclhack.def''. Please also send relevant
information to gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org and,
please, to me: bkorb@gnu.org.
Once you have made your fix, it is necessary to have at least one
test for it. Specify the test with a "test_text" entry. Run
"make check" in the fixinc directory to verify both that your fix
works (by correctly altering your test text) and that your fix
does not suppress the work of other fixes. You should readily
be able to verify this as the "make check" process will print out
context diffs of fixed files. If everything looks fine, you can
either use the diffs for a patch to the baseline files, or simply
copy the result files (in the "tests/res/" subdirectory) into the
baseline directory ("tests/base").
Here are the rules for making fixes in the inclhack.def file:
0. If you are not the fixincludes maintainer, please send that
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment