This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/24975] Aliasing problems inside libstdc++
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Nov 2005 15:17:44 -0000
- Subject: [Bug libstdc++/24975] Aliasing problems inside libstdc++
- References: <bug-24975-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #16 from pcarlini at suse dot de 2005-11-22 15:17 -------
(In reply to comment #15)
> So that leaves us with basic_string and it's problems. What do you suggest to
> vendors needing ABI compatibility?
I'm still trying to figure out whether we can do something not breaking the
ABI. Honestly, I think we should first figure out whether this specific cast
really causes problems or not. If it does, then we should raise the priority of
the issue to the highest level and probably it warrants an ABI breakage (for
4.2). If it doesn't and/or we are not ready to break the ABI, probably tweaking
the compiler to spill warnings to the face of the user is not an appropriate
action.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24975