This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 4.2 more strict check for "function called through a non-compatible type"
- From: Ryan Hill <dirtyepic at gentoo dot org>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 25 Mar 2007 22:36:46 -0600
- Subject: Re: gcc 4.2 more strict check for "function called through a non-compatible type"
- References: <44AA67AE.4070509@ptci.ru> <m3lkr9e1h1.fsf@localhost.localdomain> <17578.43651.892156.272070@zebedee.pink> <m3d5cldsl8.fsf@localhost.localdomain> <17579.35051.492454.869315@zebedee.pink> <m3zmfocfb1.fsf@localhost.localdomain> <m3wtasytkb.fsf@localhost.localdomain> <44AC95B9.9000001@codesourcery.com> <4601FE6C.60108@gentoo.org> <m3tzwb5y9j.fsf@localhost.localdomain>
Ian Lance Taylor wrote:
> Ryan Hill <dirtyepic@gentoo.org> writes:
>> Was there ever any action on this? AFAICS consensus was that the trap
>> would be removed and this behaviour be documented as an extension.
>> There was a bit more discussion of how exactly the documentation would
>> be worded[i] and the thread petered out. Fast forwarding to today the
>> abort is still present and the 4.2 branch (4.2.0-pre20070317 (rev.
>> 123016)) is still unable to build a working openssl (0.9.8e).
> I don't think anything happened with this.
>
> Is there a gcc bug report open about it? If so, Mark can bump up the
> priority.
I couldn't find one so I've filed PR #31359. Apologies if it's a duplicate.
--
where to now? if i had to guess
dirtyepic gentoo org i'm afraid to say antarctica's next
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8)