This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch] libstdc++/19664

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: libstdc++ at gcc dot gnu dot org
Date: Thu, 26 May 2005 11:48:32 -0500
Subject: Re: [Patch] libstdc++/19664
References: <428E1D70.7010705@suse.de><20050520171751.59aac887@belmont.artheist.org><428E6290.4060802@suse.de><20050520173408.62f545cf@belmont.artheist.org><428E671A.8020809@suse.de><20050520183003.5d9b2ab8@belmont.artheist.org><4290B1A7.5030803@suse.de><20050526015015.7a4b99f6.bkoz@redhat.com><42957C5C.1030208@suse.de>

> Yes ;) My point - sorry about the misunderstanding, maybe due to my bad
> english - was that you *need x86_64* to reproduce the above. Also
> affects other primary targets.

Is there a way to show the visibility issue failing reliably on all
targets with libstdc++? There must be, since this is a bug....

-benjamin

Follow-Ups:
- Re: [Patch] libstdc++/19664
  - From: Paolo Carlini

References:
- [Patch] libstdc++/19664
  - From: Paolo Carlini
- Re: [Patch] libstdc++/19664
  - From: Benjamin Kosnik
- Re: [Patch] libstdc++/19664
  - From: Paolo Carlini
- Re: [Patch] libstdc++/19664
  - From: Benjamin Kosnik
- Re: [Patch] libstdc++/19664
  - From: Paolo Carlini
- Re: [Patch] libstdc++/19664
  - From: Benjamin Kosnik
- Re: [Patch] libstdc++/19664
  - From: Paolo Carlini
- Re: [Patch] libstdc++/19664
  - From: Benjamin Kosnik
- Re: [Patch] libstdc++/19664
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]