This is the mail archive of the gcc-help@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: [gcc front end] problem with -O* flags

From: Andi Hellmund <mail at andihellmund dot com>
To: Philip Herron <redbrain at gcc dot gnu dot org>
Cc: charfi asma <charfiasma at yahoo dot fr>, gcc-help at gcc dot gnu dot org
Date: Mon, 20 Jun 2011 00:59:57 +0200
Subject: Re: [gcc front end] problem with -O* flags
References: <67917.82833.qm@web28504.mail.ukl.yahoo.com> <BANLkTimJhOPgxBxe4KCrd6HN15Gmp872Zw@mail.gmail.com>

Hey Asma,

To be fair it could be a problem with the gcc sources your compiling
with that was maybe fixed in the next commit or something.

I agree with Phil that your GENERIC code looks good. Just for future postings, whenever you face a segmentation fault and you are unsure about the root cause of the fault, it would be beneficial to always list the GCC version (e.g. 4.6.0, trunk) that you faced your problems with. By knowing the exact version, we would possibly be able to reproduce your problems somehow.

So, which version of GCC are you facing your problems with?

git add remote gcc git://gcc.gnu.org/git/gcc.git
git fetch gcc
git merge gcc/master

And make clean&& make

If it's trunk then I would recommend to follow Phil's approach and get the newest version. The trunk heavily is under development and might be broken or unstable until it becomes a release version. If it's not the trunk, then please let us know so that we could have a closer look again ...

Best regards,
Andi

Follow-Ups:
- Re : [gcc front end] problem with -O* flags
  - From: charfi asma

References:
- [gcc front end] problem with -O* flags
  - From: charfi asma
- Re: [gcc front end] problem with -O* flags
  - From: Philip Herron

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