LKML Archive on
help / color / mirror / Atom feed
From: "David Schwartz" <>
To: "Linux-Kernel@Vger. Kernel. Org" <>
Subject: RE: About GCC4 Optimization
Date: Sat, 24 Mar 2007 22:07:05 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> So what gcc does may be technically legal, but it's still a horribly
> bad thing to do. Sadly, some gcc people seem to care more
> about "letter
> of the law" than "sanity and quality of implementation".

You know, it would be one thing if they were consistent. A policy that, by
default, you get all the optimizations the relevant standards allow wouldn't
be a problem. But they do this when they feel like it, and they disable
significant optimizations even where the standards allow them when they feel
like that.

See, for example:

"You cannot create code that works with this option and doesn't work without
it except by violating the POSIX standard. So POSIX code should not have
this option enabled by default -- it's a pure pessimization." Yet the option
is on by default when -pthreads is specified.


PS: Yes, I'm still pissed about this. ;)

  reply	other threads:[~2007-03-25  5:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25  3:32 keyboard.c: Stop flooding dmesg with useless warnings Parag Warudkar
2007-03-25  3:38 ` Parag Warudkar
     [not found]   ` <BAY144-F24481F006CCA5D5D74D6F4DF680@phx.gbl>
2007-03-25  4:28     ` About GCC4 Optimization Linus Torvalds
2007-03-25  5:07       ` David Schwartz [this message]
2007-03-25  4:31     ` Andrew Morton
2007-03-25  5:15   ` keyboard.c: Stop flooding dmesg with useless warnings Dmitry Torokhov
2007-03-25  5:27     ` Parag Warudkar
2007-03-25  5:29       ` Dmitry Torokhov
2007-03-25  5:35         ` Parag Warudkar
2007-03-25  9:16           ` Jiri Kosina
2007-03-25 14:32             ` Parag Warudkar

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='RE: About GCC4 Optimization' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).