From: Jon Oberheide <jon@oberheide.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Daniel Jacobowitz <dan@debian.org>,
Vojtech Pavlik <vojtech@suse.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Some cleanup patches for: '...lvalues is deprecated'
Date: Tue, 27 Jul 2004 12:31:24 -0400 [thread overview]
Message-ID: <1090945884.30149.1.camel@dionysus> (raw)
In-Reply-To: <40FB87C400003E92@ocpmta3.freegates.net>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
On Tue, 2004-07-27 at 17:59 +0200, Joel Soete wrote:
> Marcelo,
>
> Thanks first for your attention.
> Sorry also for delaying this works but I was a bit busy elsewhere.
>
> > -- Original Message --
> > Date: Tue, 27 Jul 2004 09:54:32 -0300
> > From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
> > To: Joel Soete <soete.joel@tiscali.be>
> > Cc: Daniel Jacobowitz <dan@debian.org>,
> > Vojtech Pavlik <vojtech@suse.cz>,
> > Linux Kernel <linux-kernel@vger.kernel.org>
> > Subject: Re: Some cleanup patches for: '...lvalues is deprecated'
> >
> >
> > On Mon, Jul 05, 2004 at 01:59:21PM +0200, Joel Soete wrote:
> > > Hello Daniel,
> > >
> > > > > So just use
> > > > >
> > > > > buffer++;
> > > > >
> > > > > here, and the intent is then clear.
>
> > > >
> > > > Except C does not actually allow incrementing a void pointer, since
> > > > void does not have a size.
> > > That make better sense to me because aifair a void * was foreseen to
> pass
> > > any kind of type * as actual parameter?
> > > (So as far as I understand, the aritthm pointer sould be dynamic for
> the
> > > best 'natural' behaviour?)
> > >
> > > > You can't do arithmetic on one either. GNU
> > > > C allows this as an extension.
> > > >
> > > > It's actually this, IIRC:
> > > > buffer = ((char *) buffer) + 1;
> >
> > Joel,
> >
> > It seems the current code is working perfectly, generating correct
> > asm code.
> >
> > Could you come up with a good enough reason to do this cleanup (as far
> as
> >
> > I am concerned) in 2.4.x series?
> >
> My first attention was to cleanup some warning of type "use of cast expression
> as lvalue is deprecated"
> with gcc-3.3.4. But afaik, right now, there are just few warning which didn't
> break the asm code.
FYI, lvalue casts are treated as errors in gcc 3.5.
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-07-27 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 12:53 Some cleanup patches for: '...lvalues is deprecated' Joel Soete
2004-07-03 20:56 ` Vojtech Pavlik
2004-07-03 21:39 ` Joel Soete
2004-07-03 21:45 ` Vojtech Pavlik
2004-07-05 5:10 ` Daniel Jacobowitz
2004-07-05 8:59 ` David Vrabel
2004-07-05 11:59 ` Joel Soete
2004-07-27 12:54 ` Marcelo Tosatti
2004-07-27 15:59 ` Joel Soete
2004-07-27 15:59 ` Joel Soete
2004-07-27 16:31 ` Jon Oberheide [this message]
2004-07-30 9:11 ` Joel Soete
2004-07-30 12:51 ` Joel Soete
2004-07-30 17:29 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2004-07-31 8:41 Mikael Pettersson
2004-08-01 10:40 ` Adrian Bunk
2004-08-02 11:34 Mikael Pettersson
2004-08-02 23:08 ` Adrian Bunk
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=1090945884.30149.1.camel@dionysus \
--to=jon@oberheide.org \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=soete.joel@tiscali.be \
--cc=vojtech@suse.cz \
/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.