public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Art Haas <ahaas@airmail.net>
To: linux-kernel@vger.kernel.org
Subject: Is -fno-strict-aliasing still needed?
Date: Mon, 10 Feb 2003 14:04:34 -0600	[thread overview]
Message-ID: <20030210200434.GA376@debian> (raw)

Hi.

I ask because I've just built a kernel without using that flag -
linus-2.5 BK from this morning, probably missing the 2.5.60 release by
a few hours. I'm now running with the kernel, and things are working
normally. So, my success with my strictly aliased kernel has made me curious
if the continuing use of the flag has outlived its usefulness. I'm
running on i586, compiling with gcc-3.2.2 (CVS). Possibly the flag is
needed for other chipsets or older compilers, or particular bits of code
that I don't compile. Still, I thought I'd ask and see. Maybe other
people can try building without '-fno-strict-aliasing' and see what sort
of results they get.

I'm not including my config file to save space, but can send it if
asked.

Art Haas
-- 
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
 -- Benjamin Franklin, Historical Review of Pennsylvania, 1759

             reply	other threads:[~2003-02-10 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 20:04 Art Haas [this message]
2003-02-11  7:14 ` Is -fno-strict-aliasing still needed? Horst von Brand
2003-02-11  9:12   ` Andreas Schwab
2003-02-11  9:39     ` Horst von Brand
2003-02-11  9:45       ` Andreas Schwab
2003-02-11 10:24   ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2003-02-11 19:52 Albert Cahalan

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=20030210200434.GA376@debian \
    --to=ahaas@airmail.net \
    --cc=linux-kernel@vger.kernel.org \
    /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