public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/19060] fstream.tellp() result not changed after some output
Date: Fri, 31 Dec 2004 11:08:00 -0000 [thread overview]
Message-ID: <20041231110758.24648.qmail@sourceware.org> (raw)
In-Reply-To: <20041217182932.19060.wanderer@rsu.ru>
------- Additional Comments From pcarlini at suse dot de 2004-12-31 11:07 -------
In my opinion, this is definitely a (target dependent) code generation bug,
rather serious, if confirmed. As such, we should do our best to reduce it
and recategorize in the right way. Any chance you can try to reduce it to a
short, pure c++ snippet? The relevant library code is quite straightforward.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19060
next prev parent reply other threads:[~2004-12-31 11:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 18:29 [Bug libstdc++/19060] New: " wanderer at rsu dot ru
2004-12-17 18:31 ` [Bug libstdc++/19060] " wanderer at rsu dot ru
2004-12-17 18:31 ` wanderer at rsu dot ru
2004-12-17 18:33 ` pinskia at gcc dot gnu dot org
2004-12-17 18:44 ` wanderer at rsu dot ru
2004-12-18 20:08 ` wanderer at rsu dot ru
2004-12-19 0:03 ` pcarlini at suse dot de
2004-12-24 0:05 ` wanderer at rsu dot ru
2004-12-31 11:08 ` pcarlini at suse dot de [this message]
2004-12-31 17:13 ` wanderer at rsu dot ru
2004-12-31 17:15 ` wanderer at rsu dot ru
2004-12-31 17:16 ` wanderer at rsu dot ru
2004-12-31 17:17 ` wanderer at rsu dot ru
2004-12-31 17:58 ` wanderer at rsu dot ru
2004-12-31 17:58 ` wanderer at rsu dot ru
2004-12-31 17:59 ` wanderer at rsu dot ru
2004-12-31 18:20 ` pinskia at gcc dot gnu dot org
2004-12-31 18:29 ` pcarlini at suse dot de
2004-12-31 18:39 ` wanderer at rsu dot ru
2004-12-31 19:06 ` [Bug tree-optimization/19060] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-31 19:13 ` pinskia at gcc dot gnu dot org
2004-12-31 19:24 ` pcarlini at suse dot de
2004-12-31 19:27 ` pcarlini at suse dot de
2004-12-31 19:38 ` belyshev at depni dot sinp dot msu dot ru
2004-12-31 19:40 ` pinskia at gcc dot gnu dot org
2005-01-04 17:18 ` [Bug tree-optimization/19060] [4.0 Regression] Miscompiling of if and "long long" jakub at gcc dot gnu dot org
2005-01-04 18:42 ` pinskia at gcc dot gnu dot org
2005-01-14 20:57 ` wanderer at rsu dot ru
2005-01-15 9:46 ` cvs-commit at gcc dot gnu dot org
2005-01-15 12:47 ` steven at gcc dot gnu dot org
2005-01-15 12:48 ` Andreas Tobler
2005-01-15 12:48 ` toa at pop dot agri dot ch
2005-01-15 12:53 ` andreast at gcc dot gnu dot org
2005-01-15 13:05 ` andreast at gcc dot gnu dot org
2005-01-15 13:12 ` wanderer at rsu dot ru
2005-01-15 14:56 ` jakub at gcc dot gnu dot org
2005-01-15 15:06 ` wanderer at rsu dot ru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041231110758.24648.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).