From: Andrew Haley <aph@redhat.com>
To: thomas.martitz@student.HTW-Berlin.de
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problems migrating to gcc 4.4.3&eabi - apparently a gcc bug
Date: Tue, 09 Mar 2010 16:42:00 -0000 [thread overview]
Message-ID: <4B967A4D.8060905@redhat.com> (raw)
In-Reply-To: <4B9677C1.6040502@htw-berlin.de>
On 03/09/2010 04:30 PM, Thomas Martitz wrote:
> EABI IIRC only mentions changed rules for passing 64bit types. This call
> should have been the same with 4.4.3. It eventually is if the parameters
> are in a different order.
>
> If this is really a gcc bug, how should we proceed? I assume a bug
> report on bugzilla?
This is very strange. Can you make a self-contained source file that shows
the problem on its own? We need to be able to try it. It doesn't have to
run, we just have to see the source it generates.
Andrew.
next prev parent reply other threads:[~2010-03-09 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 16:31 Thomas Martitz
2010-03-09 16:42 ` Andrew Haley [this message]
2010-03-09 17:11 ` Thomas Martitz
2010-03-09 18:36 ` Andrew Haley
2010-03-09 18:54 ` Thomas Martitz
2010-03-09 19:11 ` Thomas Martitz
2010-03-09 19:39 ` John (Eljay) Love-Jensen
2010-03-09 19:44 ` Thomas Martitz
2010-03-09 19:46 ` Andrew Haley
2010-03-10 15:56 ` Ian Lance Taylor
2010-03-10 16:36 ` Thomas Martitz
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=4B967A4D.8060905@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=thomas.martitz@student.HTW-Berlin.de \
/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).