This is the mail archive of the gcc-bugs@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]

[Bug c++/71892] Recent optimization changes introduce bugs


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71892

--- Comment #12 from anton at mips dot complang.tuwien.ac.at ---
Given that they suffer from a lack of time, and have no way to know which gcc
versions you tested with, I guess most packagers would prefer it if the
configure script tells them the compiler version they should use rather than
them having to find out with trial and error (or worse, them not finding out
and releasing a broken package).  Telling them in the README or INSTALL files
is another option, but may be missed given the lack of time.

Of course, it would be preferable if the gcc maintainers applied the criteria
for production software (Linus Torvalds: "If a change results in user programs
breaking, it's a bug in the kernel. We never EVER blame the user programs. How
hard can this be to understand?") rather than those for research software, but
since they don't, software developers and packagers have to deal with the
wreckage as long as we use C and C++.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]