public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Stefan Franke" <stefan@franke.ms>
To: <gcc-help@gcc.gnu.org>
Subject: AW: C and C++ parser performing optimizations
Date: Tue, 4 Aug 2020 08:44:18 +0200	[thread overview]
Message-ID: <000301d66a2a$ad8dcb50$08a961f0$@franke.ms> (raw)
In-Reply-To: <alpine.LNX.2.20.13.2008022131370.2454@monopod.intra.ispras.ru>



> -----Ursprüngliche Nachricht-----
> Von: Alexander Monakov <amonakov@ispras.ru>
> Gesendet: Sonntag, 2. August 2020 20:41
> An: Stefan Franke <stefan@franke.ms>
> Cc: gcc-help@gcc.gnu.org
> Betreff: Re: C and C++ parser performing optimizations
> 
> On Sun, 2 Aug 2020, Stefan Franke wrote:
> 
> > So the parser performs unwanted and uncontrollable optimizations,
> > which I consider bogus.
> 
> On occasion they are also incorrect.
> 
> My (possibly wrong or incomplete) understanding is that GCC does not have
> internal separation of mandatory simplifications that need to be done in
the
> frontend (like constant folding in the context of integer constant
> expressions) vs. optional simplifications (optimizing substitutions).
> So it just does both at the same time.
> 
> Alexander

Here is an example where gcc creates wrong code:

test.c:
int foo() {
  const char * const txt = "hello";
  register const char * const p asm("ecx") = txt;
  register int dx asm("edx");
  asm(" call _faa" :"=r" (dx) :"rf" (p));
}

gcc -O1 -S test.c -fdump-tree-original

The variable p gets replaced and the asm input parameters are wrong:

__asm__(" call _faa":"=r" dx:"rf" (const char * const) "hello");

Uh - oh!

Stefan


  reply	other threads:[~2020-08-04  6:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02 18:15 Stefan Franke
2020-08-02 18:40 ` Alexander Monakov
2020-08-04  6:44   ` Stefan Franke [this message]
2020-08-04  7:13     ` AW: " Alexander Monakov
2020-08-04 15:33       ` Segher Boessenkool
2020-08-24 19:06     ` Gunther Nikl
2020-08-24 19:54       ` AW: " Stefan Franke

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='000301d66a2a$ad8dcb50$08a961f0$@franke.ms' \
    --to=stefan@franke.ms \
    --cc=gcc-help@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).