public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63620] RELOAD lost SET_GOT dependency on Darwin
Date: Mon, 27 Oct 2014 13:20:00 -0000	[thread overview]
Message-ID: <bug-63620-4-q9RWg2LmKg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63620-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Stupachenko Evgeny from comment #10)

> Anyway, if call is not EBX dependent (say local call in Linux) the issue is
> not reproduced (like in example from PR63618).
> So the issue looks like Darwin dependent RA issue.

True. In Darwin case, RA allocates %eax, which is call-used register and
clobbered by the call to f128_p3. I don't see %eax saved around the call.

In Linux case, RA allocates %edi, which is call-saved.
>From gcc-bugs-return-465051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 27 13:20:53 2014
Return-Path: <gcc-bugs-return-465051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23455 invoked by alias); 27 Oct 2014 13:20:53 -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 23435 invoked by uid 48); 27 Oct 2014 13:20:49 -0000
From: "petschy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63657] New: [4.9 regression] -Wunused-variable: warning supressed by virtual dtor fn
Date: Mon, 27 Oct 2014 13:31: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: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: petschy at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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
Message-ID: <bug-63657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-10/txt/msg02072.txt.bz2
Content-length: 1704

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

            Bug ID: 63657
           Summary: [4.9 regression] -Wunused-variable: warning supressed
                    by virtual dtor fn
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: petschy at gmail dot com

The under code has two unused variables, which are references to classes. We
should have two warnings, however 4.9.1 and 5.0 trunk gives just one. 4.7.2 and
4.8.3 are ok. The second warning is supressed by the virtual dtor in Bar. Only
the dtor does the trick, if I comment it out or instead I define a plain
virtual fn, the warning appears.

g++-4.8 -Wunused-variable -c 20141022-unused_warn.cpp 
20141022-unused_warn.cpp: In function ‘void foo()’:
20141022-unused_warn.cpp:7:7: warning: unused variable ‘f’ [-Wunused-variable]
  Foo& f = getfoo();
       ^
20141022-unused_warn.cpp: In function ‘void bar()’:
20141022-unused_warn.cpp:18:7: warning: unused variable ‘b’ [-Wunused-variable]
  Bar& b = getbar();
       ^


g++-5.0.0 -Wunused-variable -c 20141022-unused_warn.cpp 
20141022-unused_warn.cpp: In function ‘void foo()’:
20141022-unused_warn.cpp:7:7: warning: unused variable ‘f’ [-Wunused-variable]
  Foo& f = getfoo();
       ^

----8<----8<----8<----
class Foo 
{
};
Foo& getfoo();
void foo()
{
        Foo& f = getfoo();
}

class Bar
{
        virtual ~Bar() {}
};
Bar& getbar();
void bar()
{
        Bar& b = getbar();
}
>From gcc-bugs-return-465052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 27 13:31:13 2014
Return-Path: <gcc-bugs-return-465052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28028 invoked by alias); 27 Oct 2014 13:31:12 -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 27985 invoked by uid 48); 27 Oct 2014 13:31:08 -0000
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
Date: Mon, 27 Oct 2014 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: howarth at bromo dot med.uc.edu
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-63610-4-I7lwUnaRxn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63610-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: 2014-10/txt/msg02073.txt.bz2
Content-length: 376

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

--- Comment #9 from howarth at bromo dot med.uc.edu ---
Alternatively, you can just make sure you don't set MACOSX_DEPLOYMENT_TARGET in
your shell.

Also mote that gmp, mpfr and mpc also suffer from this bug and, if built on
10.10, should either have their configure scripts patched or regenerated with
the fixed libtool.


  parent reply	other threads:[~2014-10-27 13:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63620-4@http.gcc.gnu.org/bugzilla/>
2014-10-22 16:36 ` evstupac at gmail dot com
2014-10-22 23:20 ` evstupac at gmail dot com
2014-10-26 18:38 ` ubizjak at gmail dot com
2014-10-27  8:05 ` izamyatin at gmail dot com
2014-10-27 10:08 ` evstupac at gmail dot com
2014-10-27 12:10 ` evstupac at gmail dot com
2014-10-27 13:20 ` ubizjak at gmail dot com [this message]
2014-10-29 13:41 ` enkovich.gnu at gmail dot com
2014-10-30  7:33 ` law at redhat dot com
2014-10-30 16:01 ` vmakarov at gcc dot gnu.org
2014-10-30 16:50 ` vmakarov at gcc dot gnu.org
2014-10-30 16:56 ` law at redhat dot com
2014-10-30 18:27 ` vmakarov at gcc dot gnu.org
2014-10-31 11:13 ` ubizjak at gmail dot com
2014-10-31 19:05 ` ubizjak at gmail dot com
2014-10-31 20:03 ` uros at gcc dot gnu.org
2014-10-31 21:56 ` uros at gcc dot gnu.org
2014-11-05  9:32 ` ubizjak at gmail dot com
2014-11-09 16:45 ` vmakarov at gcc dot gnu.org
2014-11-10 21:33 ` vmakarov at gcc dot gnu.org
2014-11-10 23:36 ` ubizjak at gmail dot com

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-63620-4-q9RWg2LmKg@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).