This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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]

"Bug" only with Clang

From: Daniel Frey <d dot frey at gmx dot de>
To: gcc-help <gcc-help at gcc dot gnu dot org>
Date: Tue, 26 Feb 2013 22:37:38 +0100
Subject: "Bug" only with Clang

While using Clang++ 3.2 with libstdc++ from GCC 4.7, I ran into a problem which was discussed at StackOverflow <http://stackoverflow.com/q/15098174>. A fix in libstdc++ seems easily possible, but first: Should I create a bug report for things that actually work with GCC and only break with Clang? Or does libstdc++ accept only bugs exposed with GCC?

Daniel

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Follow-Ups:
- Re: "Bug" only with Clang
  - From: Jonathan Wakely

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