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]

Re: optimization/9904: aliasing problem


Old Synopsis: aliasing proböem
New Synopsis: aliasing problem

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Mon Mar  3 15:01:24 2003
State-Changed-Why:
    Without the functions that initialize the variables used in
    the if-clauses, it is hard to tell where the problem comes
    from. It would be great if you could find a self-contained
    testcase. Also, if you send in code like this, maybe try to
    give functions and variables names that are simpler
    to read -- for examples like yours maybe 3 or 4 characters,
    not 30 or 40.
    
    Aliasing problems are a constant source for wrong reports
    we receive, just as well as for problems in the compiler.
    I don't know into which category yours falls, but make
    sure you read the respective sections in the manual.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9904


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