All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
To: "valdis.kletnieks@vt.edu" <valdis.kletnieks@vt.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: [PATCH] make fs/reiser4/search.c compile with gcc 4.0
Date: Wed, 22 Sep 2004 21:03:45 +0200	[thread overview]
Message-ID: <2f4958ff0409221203524cabb9@mail.gmail.com> (raw)
In-Reply-To: <200409221859.i8MIxb7h014797@turing-police.cc.vt.edu>

On Wed, 22 Sep 2004 14:59:37 -0400, valdis.kletnieks@vt.edu
<valdis.kletnieks@vt.edu> wrote:
> On Wed, 22 Sep 2004 20:45:55 +0200, =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= said:
> 
> > I know gcc 4.0 is still in it's alphas.
> > Obvious solution is to move function declared in other function
> > up-wards. Since it's static anyway, it won't make any diffrence.
> > Please consider applying to repo.
> 
> I'm not sure it's a good idea to be trying to "fix" reiser4 code to compile
> with an alpha compiler, at least without a *very* firm commitment from the gcc
> crew that this *is* a real error in the reiser4 code and not a bug in gcc
> causing a spurious message.
> 
> Why does this code compile cleanly with gcc 3.x and fail with a 4.0 alpha?
> Without knowing that, it's *STUPID* to change the code to suit the alpha...

This code uses stuppid gcc extension, that is not present in gcc 4.0.
There is no reason to keep it that way in sources, at least I didn't found any.
Function is static anyway, so symbos are not going to be exported.
The fact that gcc 4.0 is not compiling it, is just another excuse to move it.
There is at least one more that kinda bug in kernel.

-- 
GJ

  reply	other threads:[~2004-09-22 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 18:45 [PATCH] make fs/reiser4/search.c compile with gcc 4.0 Grzegorz Jaśkiewicz
2004-09-22 18:59 ` Valdis.Kletnieks
2004-09-22 19:03   ` Grzegorz Jaśkiewicz [this message]
2004-09-22 19:09     ` Valdis.Kletnieks

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=2f4958ff0409221203524cabb9@mail.gmail.com \
    --to=gryzman@gmail.com \
    --cc=reiserfs-list@namesys.com \
    --cc=valdis.kletnieks@vt.edu \
    /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.