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

Re: [PATCH] Handle weak symbols



Franz --

I have looked at this problem in more detail, and I am not convinced
it can actually occur in the current sources.  We are going to need a
test-case to convince me that we need to do something here for the
branch.  It cannot occur in some of the obvious places (like
delete_null_pointer_checks, which insists on having a use of the MEM
before eliminating a future check), or loop, where as far as I can
tell, we only move the possibly-trapping instruction out of the loop
if we are sure it will be executed anyhow.

Bottom line: I'm not going to do anything that might destabilize the
3.0 branch to fix a possibly non-existant bug that's not a regression
from GCC 2.95.x.

The mainline is another story.  Please file a GNATS report that
indicates that rtx_addr_can_trap_p is broken in this respect, so that
we remember to fix this in the future.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com


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