public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/9780] issues with time_get, time_put not being tied to correct _punct facet.
       [not found] <bug-9780-4@http.gcc.gnu.org/bugzilla/>
@ 2023-05-16 19:41 ` pinskia at gcc dot gnu.org
  0 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-05-16 19:41 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|bkoz at gcc dot gnu.org            |unassigned at gcc dot gnu.org

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Reassining since Benjamin has not been active in GCC development for a few
years now.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libstdc++/9780] issues with time_get, time_put not being tied to correct _punct facet.
       [not found] <20030220183600.9780.bkoz@redhat.com>
  2003-12-05  3:16 ` pinskia at gcc dot gnu dot org
  2003-12-05  7:00 ` bkoz at redhat dot com
@ 2003-12-19 10:01 ` pinskia at gcc dot gnu dot org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-12-19 10:01 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-12-19 09:58 -------
Suspending based on Benjamin's comments.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |SUSPENDED
   Target Milestone|3.4.0                       |---


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9780


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libstdc++/9780] issues with time_get, time_put not being tied to correct _punct facet.
       [not found] <20030220183600.9780.bkoz@redhat.com>
  2003-12-05  3:16 ` pinskia at gcc dot gnu dot org
@ 2003-12-05  7:00 ` bkoz at redhat dot com
  2003-12-19 10:01 ` pinskia at gcc dot gnu dot org
  2 siblings, 0 replies; 4+ messages in thread
From: bkoz at redhat dot com @ 2003-12-05  7:00 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From bkoz at redhat dot com  2003-12-05 07:00 -------
Subject: Re:  issues with time_get, time_put not being
 tied to correct _punct facet.

>Any news on this.

this is a fatal flaw in the standard. It can be worked around, much like
money_get and money_put are able to be used: by also imbuing the
moneypunct (and here, __timepunct) facet.

You can suspend this if you'd like.

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9780


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libstdc++/9780] issues with time_get, time_put not being tied to correct _punct facet.
       [not found] <20030220183600.9780.bkoz@redhat.com>
@ 2003-12-05  3:16 ` pinskia at gcc dot gnu dot org
  2003-12-05  7:00 ` bkoz at redhat dot com
  2003-12-19 10:01 ` pinskia at gcc dot gnu dot org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-12-05  3:16 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-12-05 03:16 -------
Any news on this.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9780


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-05-16 19:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-9780-4@http.gcc.gnu.org/bugzilla/>
2023-05-16 19:41 ` [Bug libstdc++/9780] issues with time_get, time_put not being tied to correct _punct facet pinskia at gcc dot gnu.org
     [not found] <20030220183600.9780.bkoz@redhat.com>
2003-12-05  3:16 ` pinskia at gcc dot gnu dot org
2003-12-05  7:00 ` bkoz at redhat dot com
2003-12-19 10:01 ` pinskia at gcc dot gnu dot org

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).