From: Jon Oberheide <jon@oberheide.org>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH 2.4] gcc-3.4 more fixes
Date: Mon, 23 Aug 2004 15:07:32 -0400 [thread overview]
Message-ID: <1093288052.17313.11.camel@dionysus> (raw)
In-Reply-To: <4129F0C5.3040309@ttnet.net.tr>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Mon, 2004-08-23 at 16:27 +0300, O.Sezer wrote:
> > Ozkan,
> >
> > This are just warning fixes right?
> >
> > I dont like this patches, that is, I'm not confident about them.
> >
> > Let the warnings be.
>
> For gcc-3.4 they're warnings. For gcc-3.5 they'll cause compiler
> failures (that's what mikpe says on cset-1.1490, too)
Correct, l-value casts are treated as errors in 3.5.
"The cast-as-lvalue, conditional-expression-as-lvalue and compound-
expression-as-lvalue extensions, which were deprecated in 3.3.4 and 3.4,
have been removed." - http://gcc.gnu.org/gcc-3.5/changes.html
Regards,
Jon Oberheide
--
Jon Oberheide <jon@oberheide.org>
GnuPG Key: 1024D/F47C17FE
Fingerprint: B716 DA66 8173 6EDD 28F6 F184 5842 1C89 F47C 17FE
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-23 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 13:27 [PATCH 2.4] gcc-3.4 more fixes O.Sezer
2004-08-23 19:07 ` Jon Oberheide [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-23 13:41 O.Sezer
2004-08-23 12:34 ` Marcelo Tosatti
2004-08-23 14:13 ` O.Sezer
2004-08-23 13:11 ` Marcelo Tosatti
2004-08-23 22:18 ` Jeff Garzik
2004-08-23 22:34 ` O.Sezer
2004-08-23 16:10 ` O.Sezer
2004-08-05 19:54 O.Sezer
2004-08-06 20:09 ` O.Sezer
2004-08-23 11:35 ` Marcelo Tosatti
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=1093288052.17313.11.camel@dionysus \
--to=jon@oberheide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=sezeroz@ttnet.net.tr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.