public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bernd Paysan <bernd.paysan@gmx.de>
To: gcc-gnats@gcc.gnu.org
Subject: c/8092: -fno-gcse doesn't fix computed goto problems in GCC 3.2
Date: Mon, 30 Sep 2002 01:26:00 -0000	[thread overview]
Message-ID: <200209301018.53737.bernd.paysan@gmx.de> (raw)


>Number:         8092
>Category:       c
>Synopsis:       -fno-gcse doesn't fix computed goto problems in GCC 3.2
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 30 01:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bernd Paysan
>Release:        3.2
>Organization:
=20
>Environment:
System: Linux cohen 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 unkno=
wn
Architecture: i686

       =20
host: i486-suse-linux-gnu
build: i486-suse-linux-gnu
target: i486-suse-linux-gnu
configured with: ../configure --enable-threads=3Dposix --prefix=3D/usr=20
--with-local-prefix=3D/usr/local --infodir=3D/usr/share/info=20
--mandir=3D/usr/share/man --libdir=3D/usr/lib=20
--enable-languages=3Dc,c++,f77,objc,java,ada --enable-libgcj=20
--with-gxx-include-dir=3D/usr/include/g++ --with-slibdir=3D/lib=20
--with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
>Description:
        The problems with computed gotos got worse. GCC now insert jumps
        to common code instead of just placing it where it belongs.
        Insertion of superfluous code is even worse. Since some
        distributions don't ship with 2.95.x any longer (like SuSE 8.1),
        this really starts becoming critical.
>How-To-Repeat:
        Install gforth from your preferred GNU mirror. Compile it. Change=
 to
        the engine directory. Type "make engine.s". Compare the results o=
f
        gcc 2.95.3 with 3.2. Be horrified. At least I am.
>Fix:
        Please don't eliminate common subexpressions by jumps to single
        instructions. Single instructions are both cheaper and faster
        than jumps to them.
       =20
        The other fix, use GCC 2.95.3, becomes more critical, as time
        goes by. People often don't have it any longer. It produces
        incompatible code (with C++), and so on.

--=20
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-09-30  8:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200209301018.53737.bernd.paysan@gmx.de \
    --to=bernd.paysan@gmx.de \
    --cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).