public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63758] liblto_plugin.so has undefined reference to _environ on OSX
Date: Thu, 27 Nov 2014 23:34:00 -0000	[thread overview]
Message-ID: <bug-63758-4-ZU10A4VUQk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63758-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
I'm not disputing that the code is wrong…
 … and the change that you've put forward looks reasonable.

However, I'm not finding it easy to reproduce any failure - I've got a cross
from darwin12 => x86-64-linux-gnu with gold-enabled binutils.  

There's no failure at either build-time or runtime for the liblto plugin.

This is not entirely surprising (at least on the host I've tried), since the
plugin is linked with -Wl,-undefined,dynamic_lookup.  This means that _environ
will be resolved from the executable.

So I'm interested in how to reproduce the effect you show in c#1
>From gcc-bugs-return-468808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 28 01:13:18 2014
Return-Path: <gcc-bugs-return-468808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15039 invoked by alias); 28 Nov 2014 01:13:18 -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 14989 invoked by uid 48); 28 Nov 2014 01:13:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64096] std::list, set and map violate a rule about allocator::construct
Date: Fri, 28 Nov 2014 01:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
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-64096-4-ixnKNyNceU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64096-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-11/txt/msg03280.txt.bz2
Content-length: 765

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to rylai from comment #0)
> As we can see, std::list implementation tries to call construct for whole
> list node (U = std::_List_node<int>),

This is already fixed on the SVN trunk, which will be GCC 5.

> and std::set and map (and also
> multiset and multimap) call it for right type (int or std::pair<const int,
> int>), but from rebinded allocator (T = std::_Rb_tree_node<int>).

I've discussed this extensively with the main author of  the C++11 allocator
proposals and other members of the committee. The standard is supposed to allow
that, the fact it doesn't is a defect, see
http://cplusplus.github.io/LWG/lwg-active.html#2218


  parent reply	other threads:[~2014-11-27 23:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  0:14 [Bug other/63758] New: " roland at gnu dot org
2014-11-06  0:17 ` [Bug other/63758] " roland at gnu dot org
2014-11-06  9:44 ` rguenth at gcc dot gnu.org
2014-11-27 23:34 ` iains at gcc dot gnu.org [this message]
2014-12-22 13:09 ` iains at gcc dot gnu.org
2015-09-03 12:42 ` nickc at redhat dot com
2015-09-03 13:44 ` iains at gcc dot gnu.org
2015-09-03 18:08 ` egall at gwmail dot gwu.edu
2015-09-07 15:27 ` iains at gcc dot gnu.org
2015-10-18 10:34 ` iains 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-63758-4-ZU10A4VUQk@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).