public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53273] New: test-cases suffer from cross-function optimizations with no way to mark limits
Date: Tue, 08 May 2012 03:07:00 -0000	[thread overview]
Message-ID: <bug-53273-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53273

             Bug #: 53273
           Summary: test-cases suffer from cross-function optimizations
                    with no way to mark limits
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
        Depends on: 53272
              Host: x86_64-unknown-linux-gnu
            Target: crisv32-*


+++ This bug was initially created as a clone of Bug #53272 +++

See PR53272#c1 and the URL.
Putting a function together with main and auxiliary functions causes different
code than when put in separate files (difference present in the .expand dump),
despite adding all currently known attributes to stop that (noinline, noclone,
asm ("")).  If this is deliberate, there must be a future-proof way to stop
such cross-effects, if non-deliberate, it should just be fixed.

Repeat by compiling the test-cases at the URL both separately (at least the
-1.c file) and put in one file, for e.g. crisv32-elf.  Observe differences in
the .expand dump for the rtc_update_irq_enable function when compiled at -O2.


             reply	other threads:[~2012-05-08  2:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  3:07 hp at gcc dot gnu.org [this message]
2012-05-08 23:42 ` [Bug tree-optimization/53273] " hp at gcc dot gnu.org
2012-05-08 23:48 ` hp at gcc dot gnu.org
2012-05-09  0:02 ` hubicka at gcc dot gnu.org
2012-05-09  0:02 ` hp at gcc dot gnu.org
2012-05-09  0:14 ` hp at gcc dot gnu.org
2012-05-09  3:13 ` hp at gcc dot gnu.org
2024-03-16 20:58 ` pinskia at gcc dot gnu.org
2024-03-16 23:59 ` hp at gcc dot gnu.org
2024-03-17  4:43 ` pinskia at gcc dot gnu.org

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=bug-53273-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).