From: Maxim Grigoriev <maxim@tensilica.com>
To: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: Some GDB files won't compile with GCC 4.1, when -Werror is used
Date: Tue, 25 Jul 2006 06:19:00 -0000 [thread overview]
Message-ID: <44C57B3E.1050401@hq.tensilica.com> (raw)
In-Reply-To: <20060725005820.GA24528@nevyn.them.org>
>> I don't get this problem with gcc 4.1.2. I don't know which version of
>> GCC is more correct.
The source code looks fine to me. So it seems to be a "Red Hat
4.1.0-3"-specific (mis)behavior.
-- Maxim
Daniel Jacobowitz wrote:
> On Mon, Jul 24, 2006 at 05:41:08PM -0700, Maxim Grigoriev wrote:
>
>> Hello everyone,
>>
>> My codeline is synchronized with the main GDB CVS sources.
>> Am I the only individual who's unable to compile .../gdb/p-valprint.c
>> and .../gdb/cp-valprint.c with GCC 4.1 ?
>> Host is i686-pc-linux-gnu.
>>
>>
>>>>>>> uname -a
>>>>>>>
>> Linux .... 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 i686
>> i386 GNU/Linux
>>
>>
>>>>>>> gcc --version
>>>>>>>
>> gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
>> Copyright (C) 2006 Free Software Foundation, Inc.
>>
>
> I don't get this problem with gcc 4.1.2. I don't know which version of
> GCC is more correct.
>
>
>
prev parent reply other threads:[~2006-07-25 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 0:58 Maxim Grigoriev
2006-07-25 2:00 ` Daniel Jacobowitz
2006-07-25 6:19 ` Maxim Grigoriev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C57B3E.1050401@hq.tensilica.com \
--to=maxim@tensilica.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox