public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: danglin@gcc.gnu.org
To: danglin@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, ross.alexander@uk.neceur.com
Subject: Re: middle-end/4844: Code generation bug for hppa64
Date: Thu, 21 Nov 2002 17:33:00 -0000 [thread overview]
Message-ID: <20021116002720.27399.qmail@sources.redhat.com> (raw)
Synopsis: Code generation bug for hppa64
Responsible-Changed-From-To: unassigned->danglin
Responsible-Changed-By: danglin
Responsible-Changed-When: Fri Nov 15 16:27:20 2002
Responsible-Changed-Why:
Assigned.
State-Changed-From-To: open->feedback
State-Changed-By: danglin
State-Changed-When: Fri Nov 15 16:27:20 2002
State-Changed-Why:
Please confirm that this is still a problem with 3.3.
The small testcase is malformed for hppa64. On hppa64,
structs with a single field are treated as an aggregrate.
Thus, when a BIGNUM is passed as an argument, the int field
is left justfied. This has changed since the date of the
report.
There is no testcase for the actual problem.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4844
next reply other threads:[~2002-11-16 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 17:33 danglin [this message]
2003-03-11 22:51 neroden
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=20021116002720.27399.qmail@sources.redhat.com \
--to=danglin@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=ross.alexander@uk.neceur.com \
/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).