linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Nix <nix@esperi.org.uk>
Cc: uml <uml@dot1q.net>, roland <for_spam@gmx.de>,
	uml-user <user-mode-linux-user@lists.sourceforge.net>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [uml-user] SuSE 9.1 host + 2.4.26 Kernel + GCC 3.3.3 similarities to 2.6.6!?
Date: Wed, 16 Jun 2004 21:09:57 +0200	[thread overview]
Message-ID: <200406162109.57341.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <87oenle40x.fsf@amaterasu.srvr.nix>

Alle 08:20, martedì 15 giugno 2004, Nix ha scritto:
> On Mon, 14 Jun 2004, BlaisorBlade mused:

> > Well, ok, more hints, the first possible answer to this one seems to be
> > that SuSE enables -funit-at-a-time:
>
> (unsurprising, given that -funit-at-a-time's primary author is jh@suse ;} )

Well, someone following gcc development! Compliments! Do you think, too that 
SuSE gcc is a pre-release or heavily patched?

> Yep, -funit-at-a-time will definitely break kernels that aren't
> expecting it, both because of elision of unused statics and because some
> arches depend on emission of asm's at the top level to emit stuff in the
> same order in generated code, and with -funit-at-a-time this just
> doesn't happen anymore. (I don't think i386 is such an architecture,
> though.)

However, I would like to see a successful test-case with -fno-unit-at-a-time, 
plus understanding what are the faulting declaration (i.e. adding 
attribute_used where needed), before saying this bug is over.

> -funit-at-a-time is enabled by default for C and C++ in GCC 3.4.
>
> > This is the trick:
> The sort of thing you want to stash away in a header file and never lay
> eyes on again. :)

Well, this is already done, in the kernel: see the definition of 
attribute_used in linux/compiler-gcc*.h.

> > static const int hello ATTRIBUTE_USED  = 56;
> >
> > int main()
> > {
> >         asm(
> >         "mov hello, %eax\n"
> >         );
>
> Well, in this *specific* case, hello should be marked as clobbered,

If you mean should be marked by the coder, ok (gcc is not smart).

> which will also stop the compiler eliding it. But this *was* a contrived
> testcase...

Bye!
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-06-17 14:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-06 18:54 [uml-devel] Re: [uml-user] SuSE 9.1 host + 2.4.26 Kernel + GCC 3.3.3 similarities to 2.6.6!? roland
2004-06-06 21:33 ` uml
2004-06-07  3:37   ` uml
2004-06-13 21:58     ` Nix
2004-06-14 19:09       ` BlaisorBlade
2004-06-15  6:20         ` Nix
2004-06-16 19:09           ` BlaisorBlade [this message]
2004-06-17 15:35             ` uml
2004-06-17 17:25               ` BlaisorBlade
2004-06-17 18:10                 ` uml
2004-06-17 18:46                   ` BlaisorBlade
2004-06-17 20:00                     ` uml
2004-06-18 19:08                       ` [uml-devel] Re: [uml-user] SuSE 9.1 host + 2.4.26 Kernel + GCC 3.3.3 similarities to 2.6.6!? (2.6.7 additionally!) uml
2004-06-17 18:52             ` [uml-devel] Re: [uml-user] SuSE 9.1 host + 2.4.26 Kernel + GCC 3.3.3 similarities to 2.6.6!? Nix
     [not found] <007701c44be9$e4d7d630$dd02a8c0@ferraro>
2004-06-06 18:22 ` roland
2004-06-06 20:04   ` uml

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=200406162109.57341.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=for_spam@gmx.de \
    --cc=nix@esperi.org.uk \
    --cc=uml@dot1q.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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