This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Georg-Johann Lay <avr@gjlay.de> writes:
The reporting instructions from http://gcc.gnu.org/bugs/#need don't outline how to report bugs that only occur with -flto
Presumably, the bug to report is not a genuine LTO issue, but only because the compiler sees code/bunch of input files it does not see without -flto.
How should such problems that involve possibly many files be reported?
The key is always to provide all the information required for somebody else to recreate the problem.
Ian
The question is how to supply that information if dozens of sources are involved. Making dozens of attachments/comments?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |