linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: uml <uml@dot1q.net>,
	uml-user <user-mode-linux-user@lists.sourceforge.net>,
	user-mode-linux-devel@lists.sourceforge.net
Cc: roland <for_spam@gmx.de>
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: Thu, 17 Jun 2004 20:46:21 +0200	[thread overview]
Message-ID: <200406172046.21192.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <005201c45496$51bd3b00$dd02a8c0@ferraro>

Alle 20:10, giovedì 17 giugno 2004, hai scritto:
> Ah, I only tried adding the -fno-unit-at-a-time switch to -O2.. it seemed
> to work quite cleanly, and as well as expected by simply replacing the -O2
> with -O1 as I was previously doing.

Wow! Now we know what to do... thanks a lot!

> I'm really unsure about the attribute_used declaration, but if you can tell
> me how or what to test, I'm more than willing to give it a few dozen
> recompiles.

Well, thanks a lot for your effort and availability... but the attribute_used 
thing will be a series of little code changes, adding attribute_used to a lot 
of "static" simbols which gcc is somehow deleting. However, I cannot test 
anything since I haven't the buggy gcc. Since you have, take a broken binary 
and a working one (the only difference must be the -fno-unit-at-a-time switch 
in the right places) and run:

nm broken > list1
nm working > list2
diff -u list1 list2 > theChanges

and send me "theChanges" (I don't need nor want list1 or list2 for now, they 
are too big maybe for a 56k modem to download). With that at hand, it will 
take probably ten minutes for the fix.

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 18:56 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
2004-06-17 15:35             ` uml
2004-06-17 17:25               ` BlaisorBlade
2004-06-17 18:10                 ` uml
2004-06-17 18:46                   ` BlaisorBlade [this message]
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=200406172046.21192.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=for_spam@gmx.de \
    --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