This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: bounds checking and traps
- From: Zack Weinberg <zack at codesourcery dot com>
- To: "Jan Beulich" <JBeulich at novell dot com>
- Cc: <gcc at gcc dot gnu dot org>, <wilson at specifixinc dot com>
- Date: Fri, 13 Aug 2004 00:47:31 -0700
- Subject: Re: bounds checking and traps
- References: <s11c78cc.049@emea1-mh.id2.novell.com>
"Jan Beulich" <JBeulich@novell.com> writes:
>>Look for the code implementing __builtin_trap().
>
> Hmm - I'm not sure how I managed to overlook that.
>
>>i386.md can certainly contain OS-conditionalized code, if necessary,
>>but I think the problem is with your OS - this might as well be part
>>of the i386 ABI.
>
> There is no i386 ABI. There is an i386 SystemV ABI, an i386 Windows
> ABI, and a few (perhaps a lot) more.
Yah, and (this is what I'm saying, this is what I'm telling you) they
*all* define int #5 to have the same effect as #BR trap. Go on, prove
me wrong.
zw