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 target/66275] __attribute__((sysv_abi)) with x86_64-w64-mingw32-gcc generates incorrect code
Date: Mon, 08 Jun 2015 21:01:00 -0000	[thread overview]
Message-ID: <bug-66275-4-8t7EX5ZGqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66275-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3388 bytes --]

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

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|5.2                         |4.8.5

--- Comment #12 from Uroš Bizjak <ubizjak at gmail dot com> ---
Fixed everywhere.
>From gcc-bugs-return-488417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jun 08 22:02:25 2015
Return-Path: <gcc-bugs-return-488417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50602 invoked by alias); 8 Jun 2015 22:02:25 -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 50551 invoked by uid 48); 8 Jun 2015 22:02:21 -0000
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66448] [6 Regression] Bootstrap fails on darwin after r224161
Date: Mon, 08 Jun 2015 22:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aldyh at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-66448-4-AooZYYHPH6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66448-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66448-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-06/txt/msg00749.txt.bz2
Content-length: 1055

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

--- Comment #8 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Created attachment 35718
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id5718&actioníit
Tentative patch for issue #3

Regarding the Darwin ld64 warnings, I found one instance of a local static DIE
with two DW_AT_location's during x86-64 Linux bootstrap.  It was for something
like this:

void foo()
{
static const char msg[] = "asdf";
}

What is happening is that local statics during late dwarf are traversed twice,
once in final.c via debug_hooks->function_decl (and its subsequent local), and
once  in toplev.c as we traverse FOR_EACH_DEFINED_SYMBOL with
debug_hooks->late_global_decl.

However, the multiple DW_AT_location's never made it to the object file (on
Linux anyhow) because resolve_addr() removed one of the duplicates.

I wonder if the attached patch catches anything else in Darwin, or if it
eliminates the warning altogether.

Iain, could you try this and see if it either ICEs, or if the warnings are
removed?


      parent reply	other threads:[~2015-06-08 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 15:27 [Bug c/66275] New: " peter at cordes dot ca
2015-05-25  9:58 ` [Bug rtl-optimization/66275] " ubizjak at gmail dot com
2015-05-26 10:46 ` rguenth at gcc dot gnu.org
2015-05-26 11:09 ` ubizjak at gmail dot com
2015-06-01 19:52 ` [Bug target/66275] " ubizjak at gmail dot com
2015-06-03 15:47 ` uros at gcc dot gnu.org
2015-06-08 18:42 ` uros at gcc dot gnu.org
2015-06-08 20:07 ` uros at gcc dot gnu.org
2015-06-08 20:59 ` uros at gcc dot gnu.org
2015-06-08 21:01 ` ubizjak at gmail dot com [this message]

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-66275-4-8t7EX5ZGqv@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).