autogen version testing in fixincludes/genfixes

Hello With the autogen (GNU AutoGen) 5.11.9 on my Linux/Debian/Sid (or perhaps /Experimental) the genfixes script fail, because of the version test. The following patch corrects that. Index: fixincludes/genfixes === --- fixincludes

Re: Adding elements into tree data structure

"Iyer, Balaji V" writes: > I am trying to mark all for loop *top* labels with a integer value. > This integer value is an index to another data structure that I'm trying to > maintain. > >I just added the index value (as unsigned int) into the following data > structure (in tree.h):

RE: Adding elements into tree data structure

Hello Ian and Everyone, Here is my problem specifically. I apologize in advance if this email is long. I am trying to mark all for loop *top* labels with a integer value. This integer value is an index to another data structure that I'm trying to maintain. I just added the ind

gcc-4.4-20110607 is now available

Snapshot gcc-4.4-20110607 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20110607/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.4 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

[google] Merged gcc-4_6-branch -> google/gcc-4_6

This brings google/gcc-4_6 up to rev 174748. Validated on x86_64. Diego.

Re: strict aliasing: cast from char[] or char *

On 7 June 2011 15:39, Richard Guenther wrote: > On Tue, Jun 7, 2011 at 4:31 PM, Jonathan Wakely wrote: >> On 7 June 2011 15:20, Richard Guenther wrote: However, for my construct, which appears to be completely legal, I get a warning, which I'd like to disable.  How can I do that?  

[gimplefe] update your local trees

Ketaki, Sandeep, My last merge from trunk into gimple-front-end was incomplete. I just realized that I had failed to commit several directories. I just committed a fix, so please make sure that your local checkout is at rev 174754. Diego.

Re: What should I do to make gcc support PIC code?

On Tue, Jun 7, 2011 at 10:52 PM, Ian Lance Taylor wrote: > Liu writes: > >> Yes, I am working on a new gcc target, it almost finished but PIC and >> dynamic linking. >> They want me make the toolchain support PIC and dynamic linking. I'm >> not sure what should I do, will you show me a path? > >

Re: What should I do to make gcc support PIC code?

Liu writes: > Yes, I am working on a new gcc target, it almost finished but PIC and > dynamic linking. > They want me make the toolchain support PIC and dynamic linking. I'm > not sure what should I do, will you show me a path? [ Sorry for my earlier reply, I see now that you did also reply to t

Re: strict aliasing: cast from char[] or char *

On Tue, Jun 7, 2011 at 4:31 PM, Jonathan Wakely wrote: > On 7 June 2011 15:20, Richard Guenther wrote: >>> >>> However, for my construct, which appears to be completely legal, I get a >>> warning, which I'd like to disable.  How can I do that?  Currently I'm using >>> -Wno-strict-aliasing, but I'd

Re: strict aliasing: cast from char[] or char *

On 7 June 2011 15:20, Richard Guenther wrote: >> >> However, for my construct, which appears to be completely legal, I get a >> warning, which I'd like to disable.  How can I do that?  Currently I'm using >> -Wno-strict-aliasing, but I'd like to have a better solution.  I tried to >> cast (void*) b

[google] Merged google/main -> google/gcc-4_6

This merge brings google/gcc-4_6 up to rev 174706. Validated on x86_64. Diego.

Re: strict aliasing: cast from char[] or char *

On Tue, Jun 7, 2011 at 4:05 PM, Herman, Geza wrote: > On 06/07/2011 03:02 PM, Richard Guenther wrote: >> >> On Tue, Jun 7, 2011 at 2:58 PM, Herman, Geza  wrote: >>> >>> On 06/07/2011 12:27 PM, Richard Guenther wrote: On Tue, Jun 7, 2011 at 5:51 AM, Herman, Geza    wrote: > > Hi,

Re: strict aliasing: cast from char[] or char *

On 7 June 2011 15:05, Herman, Geza wrote: > > However, for my construct, which appears to be completely legal, I get a > warning, which I'd like to disable.  How can I do that?  Currently I'm using > -Wno-strict-aliasing, but I'd like to have a better solution.  I tried to > cast (void*) before the

Re: strict aliasing: cast from char[] or char *

On 06/07/2011 03:02 PM, Richard Guenther wrote: On Tue, Jun 7, 2011 at 2:58 PM, Herman, Geza wrote: On 06/07/2011 12:27 PM, Richard Guenther wrote: On Tue, Jun 7, 2011 at 5:51 AM, Herman, Gezawrote: Hi, Sorry, if it has been discussed before, I found a lot of information on strict alia

Re: What should I do to make gcc support PIC code?

On Tue, Jun 7, 2011 at 9:20 PM, Ian Lance Taylor wrote: > Liu writes: > >> If I want make a GNU Toolchain support PIC code and Dynamic link, >> do I need do some work on gcc? >> If I do need. What should I do? > > The GNU toolchain supports PIC and dynamic linking by default.  Are you > talking a

Re: What should I do to make gcc support PIC code?

Liu writes: > If I want make a GNU Toolchain support PIC code and Dynamic link, > do I need do some work on gcc? > If I do need. What should I do? The GNU toolchain supports PIC and dynamic linking by default. Are you talking about some new gcc target? If so, you need to give us more details.

Re: Adding arm-apple-darwin target

Erik Olofsson writes: > I have come to rely on C++0x support in GCC 4.6 and later. Until clang has > feature parity with GCC 4.6, GCC seems to be my only choice for a darwin > compiler. > > As I need to support iPhone it would seem arm-apple-darwin would be the > correct target. > > Would ther

Re: strict aliasing: cast from char[] or char *

On 06/07/2011 12:27 PM, Richard Guenther wrote: On Tue, Jun 7, 2011 at 5:51 AM, Herman, Geza wrote: Hi, Sorry, if it has been discussed before, I found a lot of information on strict aliasing in gcc, but nothing about this particular case. I'd like to code a custom container class: it has a c

Re: strict aliasing: cast from char[] or char *

On Tue, Jun 7, 2011 at 2:58 PM, Herman, Geza wrote: > On 06/07/2011 12:27 PM, Richard Guenther wrote: >> >> On Tue, Jun 7, 2011 at 5:51 AM, Herman, Geza  wrote: >>> >>> Hi, >>> >>> Sorry, if it has been discussed before, I found a lot of information on >>> strict aliasing in gcc, but nothing about

What should I do to make gcc support PIC code?

Hi all, If I want make a GNU Toolchain support PIC code and Dynamic link, do I need do some work on gcc? If I do need. What should I do? Thanks --Liu

Adding arm-apple-darwin target

Hello, I have come to rely on C++0x support in GCC 4.6 and later. Until clang has feature parity with GCC 4.6, GCC seems to be my only choice for a darwin compiler. As I need to support iPhone it would seem arm-apple-darwin would be the correct target. Would there be any interest in a patch p

Re: strict aliasing: cast from char[] or char *

On Tue, Jun 7, 2011 at 5:51 AM, Herman, Geza wrote: > Hi, > > Sorry, if it has been discussed before, I found a lot of information on > strict aliasing in gcc, but nothing about this particular case.  I'd like to > code a custom container class: it has a char[] (or dynamically allocated > "char *"

Re: strict aliasing: cast from char[] or char *

Please send questions about using GCC to gcc-h...@gcc.gnu.org, this mailing list is for discussing development of GCC, thanks. On 7 June 2011 04:51, Herman, Geza wrote: > > Here, gcc warns on the reinterpret_cast line. Which version?