From: Andi Kleen <ak@colin.muc.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix undefined/miscompiled construct in kernel parameters
Date: 15 Jun 2003 19:32:56 +0200
Date: Sun, 15 Jun 2003 19:32:56 +0200 [thread overview]
Message-ID: <20030615193256.29257@colin.muc.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306151021440.8088-100000@home.transmeta.com>; from Linus Torvalds on Sun, Jun 15, 2003 at 10:24:13AM -0700
> They are not arbitrary symbols. They are symbols in the same data
> structure, set up by the linker script. Gcc doesn't know that, but the
> fact that gcc doesn't know doesn't mean that gcc should be lazy and
> doesn't really excuse buggy code.
>
> The gcc developers you talked to are picking their legalistic noses, and
> it's sad that this isn't exactly the first time it has happened.
I tend to agree, feel free to flame them. But it doesn't help me right now
when I want to get a booting kernel. Could you merge that change or if you
prefer I can rewrite it to anonymous asm (but it will be probably more ugly).
I just need some workaround.
Thanks.
-Andi
next prev parent reply other threads:[~2003-06-15 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030615131004$6a85@gated-at.bofh.it>
[not found] ` <20030615170013$4ebc@gated-at.bofh.it>
2003-06-15 17:17 ` [PATCH] Fix undefined/miscompiled construct in kernel parameters Andi Kleen
2003-06-15 17:24 ` Linus Torvalds
2003-06-15 17:32 ` Andi Kleen [this message]
2003-06-15 17:48 ` Roman Zippel
2003-06-15 18:28 ` Andi Kleen
2003-06-15 22:56 ` Richard Henderson
2003-06-15 12:58 Andi Kleen
2003-06-15 16:52 ` Linus Torvalds
2003-06-16 0:23 ` Rusty Russell
2003-06-16 0:49 ` Richard Henderson
2003-06-16 3:55 ` Rusty Russell
2003-06-16 2:44 ` Linus Torvalds
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=20030615193256.29257@colin.muc.de \
--to=ak@colin.muc.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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