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
1eb79505
Commit
1eb79505
authored
Aug 24, 1998
by
Martin v. Löwis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update Bug Reporting to allow compression, and to recommend --save-temps
From-SVN: r21937
parent
d2d50133
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
11 deletions
+13
-11
gcc/gcc.texi
+13
-11
No files found.
gcc/gcc.texi
View file @
1eb79505
...
...
@@ -2248,11 +2248,13 @@ Please report each bug in a separate message. This makes it easier for
us
to
track
which
bugs
have
been
fixed
and
to
forward
your
bugs
reports
to
the
appropriate
maintainer
.
Do
not
compress
and
encode
any
part
of
your
bug
report
using
programs
such
as
@file{
uuencode
}
.
If
you
do
so
it
will
slow
down
the
processing
of
your
bug
.
If
you
must
submit
multiple
large
files
,
use
@file{
shar
}
,
which
allows
us
to
read
your
message
without
having
to
run
any
decompression
programs
.
If
you
include
source
code
in
your
message
,
you
can
send
it
as
clear
text
if
it
is
small
.
If
the
message
is
larger
,
you
may
compress
it
using
@file{
gzip
}
,
@file{
bzip2
}
,
or
@file{
pkzip
}
.
Please
be
aware
that
sending
compressed
files
needs
an
additional
binary
-
safe
mechanism
such
as
@code{
MIME
}
or
@code{
uuencode
}
.
There
is
a
40
k
message
limit
on
the
@samp{
egcs
-
bugs
@@cygnus
.
com
}
mailing
list
at
the
time
of
this
writing
(
August
1998
).
To
enable
someone
to
investigate
the
bug
,
you
should
include
all
these
things:
...
...
@@ -2268,12 +2270,12 @@ the bug in the current version of GNU CC.
@item
A
complete
input
file
that
will
reproduce
the
bug
.
If
the
bug
is
in
the
C
preprocessor
,
send
a
source
file
and
any
header
files
that
it
requires
.
If
the
bug
is
in
the
compiler
proper
(
@file{
cc1
}
),
run
your
source
file
through
the
C
preprocessor
by
doing
@samp{
gcc
-
E
@var{
sourcefile
}
>
@var{
outfile
}}
,
then
include
the
contents
of
@var{
outfile
}
in
the
bug
report
.
(
When
you
do
this
,
use
the
same
@samp{
-
I
}
,
@samp{
-
D
}
or
@samp{
-
U
}
options
that
you
used
in
actual
compilation
.)
requires
.
If
the
bug
is
in
the
compiler
proper
(
@file{
cc1
}
),
send
the
preprocessor
output
generated
by
adding
@samp{
-
save
-
temps
}
to
the
compilation
command
(
@pxref{
Debugging
Options
}
).
When
you
do
this
,
use
the
same
@samp{
-
I
}
,
@samp{
-
D
}
or
@samp{
-
U
}
options
that
you
used
in
actual
compilation
.
Then
send
the
@var{
input
}
.
i
or
@var{
input
}
.
ii
files
generated
.
A
single
statement
is
not
enough
of
an
example
.
In
order
to
compile
it
,
it
must
be
embedded
in
a
complete
file
of
compiler
input
;
and
the
bug
...
...
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