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
485d61a7
Commit
485d61a7
authored
Apr 06, 2004
by
Paul Brook
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* doc/sourcebuild.texi: Remove obsolete contraint on testcases.
From-SVN: r80454
parent
3984e89a
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
gcc/ChangeLog
+4
-0
gcc/doc/sourcebuild.texi
+0
-4
No files found.
gcc/ChangeLog
View file @
485d61a7
2004-04-06 Paul Brook <paul@codesourcery.com>
* doc/sourcebuild.texi: Remove obsolete contraint on testcases.
2004-04-05 Kaz Kojima <kkojima@gcc.gnu.org>
* config/sh/sh.c (prepare_move_operands): Use emit_call_insn
...
...
gcc/doc/sourcebuild.texi
View file @
485d61a7
...
...
@@ -820,10 +820,6 @@ been fixed, or whether it may be a regression, but does not give any
other
information
about
the
bug
or
where
discussion
of
it
may
be
found
.
Some
other
language
testsuites
follow
similar
conventions
.
Test
cases
should
use
@code{
abort
()
}
to
indicate
failure
and
@code{
exit
(
0
)
}
for
success
;
on
some
targets
these
may
be
redefined
to
indicate
failure
and
success
in
other
ways
.
In
the
@file{
gcc
.
dg
}
test
suite
,
it
is
often
necessary
to
test
that
an
error
is
indeed
a
hard
error
and
not
just
a
warning
---
for
example
,
where
it
is
a
constraint
violation
in
the
C
standard
,
which
must
...
...
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