From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: RE: [PATCH] fixes for building kernel 2.5.45 using Intel compiler (Ta ke 2)
Date: Thu, 31 Oct 2002 14:47:16 -0800 [thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4000EFF46CD@fmsmsx103.fm.intel.com> (raw)
> From: Nakajima, Jun [mailto:jun.nakajima@intel.com]
> Sent: Thursday, October 31, 2002 12:17 PM
>
> This is take 2 of the updated patch against 2.5.45. I'm
> asking the compiler team if someone can answer your question:
>
> > Considering that Intel largely wrote iBCS2, I guess some
> Intel person can
> > know what the standard was ;)
This is what some Intel person said:
The optimization the compiler is working around is perfectly legal.
It isn't legal C/C++ to "use" a parameter after the function has
returned.
The optimizer knows this, and that is why the code got removed. The
volatile
is necessary in order to make this kind of C code work.
The point is that once sys_iopl(unsigned long unused) returns a value,
unused is
finished. So nobody can do anything with the data associated with it after
that.
Jun
next reply other threads:[~2002-10-31 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 22:47 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 20:16 Nakajima, Jun
2002-11-01 13:20 ` Alan Cox
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=F2DBA543B89AD51184B600508B68D4000EFF46CD@fmsmsx103.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.saxena@intel.com \
--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
all inboxes | Powered by JetHome®