public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66163] [6 Regression] Not working Firefox built with LTO
Date: Mon, 18 May 2015 14:02:00 -0000	[thread overview]
Message-ID: <bug-66163-4-MaI9ZR5f6u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66163-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66163

--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
According to -fsanitize=null, there are many places in Firefox that produce
undefined behavior in followin way:

https://bugzilla.mozilla.org/show_bug.cgi?id=1165904

One common example:

    static size_t offsetOfThis() {
        JitFrameLayout* base = nullptr;
        return reinterpret_cast<size_t>(&base->argv()[0]);
    }


Martin
>From gcc-bugs-return-486539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 18 14:28:21 2015
Return-Path: <gcc-bugs-return-486539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17732 invoked by alias); 18 May 2015 14:28:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17694 invoked by uid 48); 18 May 2015 14:28:17 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66192] New: C++ static initializer unnecessary __cxa_guard_acquire for TARGET_RELAXED_ORDERING
Date: Mon, 18 May 2015 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-66192-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg01379.txt.bz2
Content-length: 919

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf192

            Bug ID: 66192
           Summary: C++ static initializer unnecessary __cxa_guard_acquire
                    for TARGET_RELAXED_ORDERING
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dje at gcc dot gnu.org
  Target Milestone: ---

// static_init.cc

int* f(void) {
  static int* p = new int;
  return p;
}

$ g++ -O2 -S -fno-exceptions static_init.cc

generates an unnecessary call to __cxa_guard_acquire on what should be the fast
path for targets with TARGET_RELAXED_ORDERING defined.  The guard should be an
atomic variable accessed with the equivalent of __atomic_load(ACQUIRE) instead
of a heavy-weight __cxa_guard_acquire() call invoking heavier-weight
synchronization.


  parent reply	other threads:[~2015-05-18 14:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 16:07 [Bug tree-optimization/66163] New: " marxin at gcc dot gnu.org
2015-05-15 16:14 ` [Bug tree-optimization/66163] " pinskia at gcc dot gnu.org
2015-05-15 16:43 ` marxin at gcc dot gnu.org
2015-05-15 19:27 ` hubicka at gcc dot gnu.org
2015-05-16  7:51 ` mpolacek at gcc dot gnu.org
2015-05-16 21:57 ` hubicka at gcc dot gnu.org
2015-05-18 11:52 ` rguenth at gcc dot gnu.org
2015-05-18 11:53 ` rguenth at gcc dot gnu.org
2015-05-18 14:02 ` marxin at gcc dot gnu.org [this message]
2015-05-18 14:32 ` hubicka at ucw dot cz
2015-05-18 14:33 ` hubicka at gcc dot gnu.org
2015-05-19  6:47 ` law at redhat dot com
2015-06-09 12:56 ` marxin at gcc dot gnu.org
2015-06-09 16:55 ` hubicka at ucw dot cz
2015-06-09 18:15 ` marxin 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-66163-4-MaI9ZR5f6u@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).