Hello,
For the code (20020611-1.c)
int p;int k;unsigned int n;
void x ()
{
unsigned int h;//line 1
h = n <= 30; //line 2
// printf("%u\n",h);
if (h)
p = 1;
else
p = 0;
if (h)
k = 1;
else
k = 0;
}
unsigned int n = 30;
ma
Output from srcdir/config.guess:
i686-pc-linux-gnu
Output from gcc -v:
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../srcdir/configure --prefix=/my_pathname/gcc4.1.1
--enable-languages=c,c++
Thread model: posix
gcc version 4.1.1
Distribution name and version: Red Hat
I was going to re-subscribe my dropped subscription to gcc-patches,
but the only links (that I can find) on gcc.gnu.org lead to the archives,
not to the subscription page. Thanks - Bruce
On 19 October 2006 15:36, Bruce Korb wrote:
> I was going to re-subscribe my dropped subscription to gcc-patches,
> but the only links (that I can find) on gcc.gnu.org lead to the archives,
> not to the subscription page. Thanks - Bruce
http://gcc.gnu.org/lists.html
Search for "Subscribing/un
On Wednesday 18 October 2006 15:45, you wrote:
>-fdump-rtl-all-details will give you an idea of how far the compiler
> gets, and thus maybe a clue to which pass runs into problems. Also, a
> backtrace from the debugger is nice to have.
Here is the backtrace from gdb:
Breakpoint 2, rtl_verify_
On Thu, Oct 19, 2006 at 07:10:27PM +0200, Frank Riese wrote:
>
> when I -fdump-rtl-all-details, I get:
>
> function8.c.104r.expand function8.c.108r.initvals function8.c.111r.jump
> function8.c.106r.locators function8.c.105r.sibling
> function8.c.109r.unshare function8.c.110r.vregs
Some
We're thinking of including these libraries in the next version of OS
X on the system so that 4.2 will work out of the box when either a) it
is released, or b) leopard is released, whichever happens last. Since
we need to keep abis stable, I was wondering if anyone planned on
changing abi o
Eric Christopher wrote on 10/19/06 17:33:
I was wondering if anyone planned on changing abi or if we can depend
on all changes not breaking the abi of these libraries?
There is nothing planned in that area, but I wouldn't want to guarantee
ABI stability. Mostly as a result of bug fixing. Sin
On Oct 19, 2006, at 2:50 PM, Diego Novillo wrote:
Eric Christopher wrote on 10/19/06 17:33:
I was wondering if anyone planned on changing abi or if we can depend
on all changes not breaking the abi of these libraries?
There is nothing planned in that area, but I wouldn't want to
guarantee A
For GCC, I've found it necessary to have a way to name local (that is,
namespace-scope 'static') variables and functions which allows more
than one such symbol to be present and have distinct mangled names.
Since the variables are 'static' there are no ABI concerns, but it
would nice to do this in
[EMAIL PROTECTED] (Geoffrey Keating) writes:
> For GCC, I've found it necessary to have a way to name local (that is,
> namespace-scope 'static') variables and functions which allows more
> than one such symbol to be present and have distinct mangled names.
Out of curiousity: why start the name w
On Wed, Oct 18, 2006 at 11:22:40PM +0200, Bernhard Fischer wrote:
> Hi,
>
> I need to check for a non-0 return value in dg-compile testcases in
> gcc.
The compiler's exit status is only known within code from the DejaGnu
product, in proc default_target_compile in DejaGnu's target.exp. If
there w
Snapshot gcc-4.0-20061019 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20061019/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.0 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On 19/10/2006, at 3:04 PM, Ian Lance Taylor wrote:
[EMAIL PROTECTED] (Geoffrey Keating) writes:
For GCC, I've found it necessary to have a way to name local (that
is,
namespace-scope 'static') variables and functions which allows more
than one such symbol to be present and have distinct mang
Geoffrey Keating wrote:
For GCC, I've found it necessary to have a way to name local (that is,
namespace-scope 'static') variables and functions which allows more
than one such symbol to be present and have distinct mangled names.
With my GCC hat on, I don't think this is desirable. For ELF at
Hi all,
I am having trouble with finding what method of a class that __comp_ctor
() would call. I have been assuming that it will call the constructor
method that has the same parameter list as the __comp_ctor () function
but this does not seem to be working.
Particulary when compiling code
Brendon Costa wrote:
basic_ofstream::basic_ofstream(int __in_chrg, void* __vtt_parm)
Can someone please help me understand why this happens?
Well looking more in the source I have found that this happens when
virtual inheritance is in play. It is used to determine which
constructor will cons
On Fri, 2006-10-20 at 06:38 +, Brendon Costa wrote:
> The other question however is still valid. If anyone knows a simple way
> to achieve this then I would love to hear it.
This is related to the ABI which you should also look at while dealing
with C++. The ABI is the IA64 C++ ABI which can
18 matches
Mail list logo
