This is the mail archive of the gcc@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: Proper way to make a one-off multi-file testcase?

From: Joern Rennecke <joernr at arc dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Jakub Jelinek <jakub at redhat dot com>, gcc at gcc dot gnu dot org
Date: Thu, 31 Jan 2008 17:27:43 +0000
Subject: Re: Proper way to make a one-off multi-file testcase?
References: <20080130211814.GB8600@elsdt-razorfish.arc.com> <20080130215125.GD24264@sunsite.mff.cuni.cz> <20080130223029.GC8600@elsdt-razorfish.arc.com> <m3sl0ej18f.fsf@localhost.localdomain>

> One issue here is that in some cases const and pure calls can get
> combined and eliminated even with attribute noinline (unless this
> changed recently).  So in addition to attribute noinline, putting an
> asm volatile ("") in the function can help make it non-pure and
> non-const.

Yes, that did the trick.

FWIW, I am using a compiler based on gcc 4.2.1 .
We (ARC) will have to work with this version for a while longer because we
are participating in the Milepost research project ( http://www.milepost.eu/ )
and not all partners were happy with going to a GPLv3 GCC when we decided
on the base version.

References:
- Proper way to make a one-off multi-file testcase?
  - From: Joern Rennecke
- Re: Proper way to make a one-off multi-file testcase?
  - From: Jakub Jelinek
- Re: Proper way to make a one-off multi-file testcase?
  - From: Joern Rennecke
- Re: Proper way to make a one-off multi-file testcase?
  - From: Ian Lance Taylor

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