Am Freitag, 3. Juni 2005 10:48 schrieb Mark Mitchell:
> DJ Delorie wrote:
> > Do we have a standard way of telling the testsuite how big target
> > types are, or some standard "this test assumes 32 bit int" dejagnu
> > flag?
>
> I don't think we have any way of doing this at present. I could be
>
> struct-layout-1_generate.c is run on the host, not on the target.
> And for hosts AFAIK GCC requires 32-bit int.
But the structures it generates assume 32-bit ints:
T(0,enum E2 a:31;,B(0,a,e2_m1,e2_0))
You can't have a 31 bit enum on a 16 bit target. You get messages
like this:
On Fri, Jun 03, 2005 at 11:14:15AM +0200, Jakub Jelinek wrote:
> On Fri, Jun 03, 2005 at 02:07:57AM -0700, Mark Mitchell wrote:
> > >Doesn't "is-effective-target ilp32" test for 32 bits int?
> >
> > Good point! I forgot about that. My brain is stuck in some other year.
> >
> > That doesn't let
On Thu, Jun 02, 2005 at 09:49:03PM -0400, DJ Delorie wrote:
>
> gcc.dg/compat/struct-layout-1_generate.c assumes sizeof(int) is 4.
> This of course fails on any target where sizeof(int) is 2. They may
> fail when sizeof(int) is 8 too, or at least they won't be testing the
> full range of possibil
On Fri, Jun 03, 2005 at 02:07:57AM -0700, Mark Mitchell wrote:
> >Doesn't "is-effective-target ilp32" test for 32 bits int?
>
> Good point! I forgot about that. My brain is stuck in some other year.
>
> That doesn't let you adjust the test based on the compiler, but it does
> let you skip test
Steven Bosscher wrote:
On Friday 03 June 2005 10:48, Mark Mitchell wrote:
DJ Delorie wrote:
Do we have a standard way of telling the testsuite how big target
types are, or some standard "this test assumes 32 bit int" dejagnu
flag?
I don't think we have any way of doing this at present. I c
On Friday 03 June 2005 10:48, Mark Mitchell wrote:
> DJ Delorie wrote:
> > Do we have a standard way of telling the testsuite how big target
> > types are, or some standard "this test assumes 32 bit int" dejagnu
> > flag?
>
> I don't think we have any way of doing this at present. I could be
> wro
DJ Delorie wrote:
Do we have a standard way of telling the testsuite how big target
types are, or some standard "this test assumes 32 bit int" dejagnu
flag?
I don't think we have any way of doing this at present. I could be
wrong, though. We could certainly add logic to compute this, using
gcc.dg/compat/struct-layout-1_generate.c assumes sizeof(int) is 4.
This of course fails on any target where sizeof(int) is 2. They may
fail when sizeof(int) is 8 too, or at least they won't be testing the
full range of possibilities.
I've noticed that quite a few testcases make these types of
as