This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/57403] A vector of volatile int doesn't work, but one of volatile void * does
- From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 24 May 2013 21:05:14 +0000
- Subject: [Bug libstdc++/57403] A vector of volatile int doesn't work, but one of volatile void * does
- Auto-submitted: auto-generated
- References: <bug-57403-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57403
Daniel KrÃgler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler@googlemail.
| |com
--- Comment #4 from Daniel KrÃgler <daniel.kruegler at googlemail dot com> ---
(In reply to Nick Maclaren from comment #2)
> That may well be true, but I can't find any such restriction in the C++
> standard. It would be a great help if the library specification weren't
> so ambiguous - in this case, it hinges around the meaning of the word
> 'type', and the unqualified word is used with at least three meanings
> in the standard.
Actually there is a miss in Table 27, where the variables T, U, and C are
described as
"any non-const object type (3.9)"
This should be corrected to
"any non-const non-volatile object type (3.9)"
I'm submitting an LWG issue for this.