public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pb@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kediger@licor.com,
	nobody@gcc.gnu.org, pb@gcc.gnu.org
Subject: Re: target/4866: [ARM; C++] doubles not passed to cout correctly
Date: Tue, 22 Jan 2002 14:47:00 -0000	[thread overview]
Message-ID: <20020122224712.7588.qmail@sources.redhat.com> (raw)

Old Synopsis: double floating pt problem with ARM cross compiler and -O2 optimization
New Synopsis: [ARM; C++] doubles not passed to cout correctly

Responsible-Changed-From-To: unassigned->pb
Responsible-Changed-By: pb
Responsible-Changed-When: Tue Jan 22 14:47:11 2002
Responsible-Changed-Why:
    .
State-Changed-From-To: open->analyzed
State-Changed-By: pb
State-Changed-When: Tue Jan 22 14:47:11 2002
State-Changed-Why:
    The problem doesn't seem to be corruption on the stack as such, but rather a failure of argument marshalling for the call to cout.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4866


             reply	other threads:[~2002-01-22 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22 14:47 pb [this message]
2002-03-22  4:09 rearnsha
2002-09-21  9:23 rearnsha

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=20020122224712.7588.qmail@sources.redhat.com \
    --to=pb@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=kediger@licor.com \
    --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).