public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Oddvar.Myrnes@stoltoffshore.no
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5241: Fstream error using the -malign-double compiler flag
Date: Sun, 06 Jan 2002 23:36:00 -0000 [thread overview]
Message-ID: <20020107073601.10679.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5241; it has been noted by GNATS.
From: Oddvar.Myrnes@stoltoffshore.no
To: rodrigc@gcc.gnu.org,
gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org,
xomy@stoltoffshore.no,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/5241: Fstream error using the -malign-double compiler flag
Date: Mon, 7 Jan 2002 08:29:15 +0100
Many Thanks. :-)
Regards
Oddvard
rodrigc@gcc.g
nu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
xomy@stoltoffshore.no
04.01.2002 cc:
19:15 Subject: Re: c++/5241: Fstream error using the -malign-double
Please compiler flag
respond to
rodrigc;
Please
respond to
gcc-bugs;
Please
respond to
gcc-prs;
Please
respond to
nobody;
Please
respond to
xomy; Please
respond to
gcc-gnats
Synopsis: Fstream error using the -malign-double compiler flag
State-Changed-From-To: feedback->closed
State-Changed-By: rodrigc
State-Changed-When: Fri Jan 4 10:15:37 2002
State-Changed-Why:
Can't reproduce problem with the FSF version of gcc 2.95.3
or gcc 3.0.3.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5241
next reply other threads:[~2002-01-07 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 23:36 Oddvar.Myrnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 6:26 Craig Rodrigues
2002-01-23 2:16 Oddvar.Myrnes
2002-01-04 10:16 Craig Rodrigues
2002-01-04 10:15 rodrigc
2002-01-02 20:13 rodrigc
2002-01-02 1:06 xomy
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=20020107073601.10679.qmail@sources.redhat.com \
--to=oddvar.myrnes@stoltoffshore.no \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).