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

Re: Reporting bugs: there is nothing to gain in frustrating reporters


Vincent Lefevre <vincent+gcc@vinc17.org> writes:

| On 2005-06-19 09:57:33 -0400, Andrew Pinski wrote:
| > Also I think GCC is not the one who is defining it either. It is
| > glibc who is defining that so complain to them instead.
| 
| Thanks for the information (I'm a bit surprised because these are gcc
| command-line options that are the first cause of these definitions).
| Is there a way to know what gcc defines and what glibc defines?

As a first approximation, you can start with the assumption that
anything having to do with the C standard library is expected to be
provided by the target system library.  GCC does some transformations
based on the standard semantics -- look for the so-called "built-ins"
in the documentation.  The options are sometime needed for the target
library to profide some functionalities, so that means that it is
close do impossible for GCC to know when a switch is selected by 
User L. but is not honored by the target library.

-- Gaby


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