public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13)
Date: Tue, 14 Sep 2004 01:14:00 -0000	[thread overview]
Message-ID: <D98B11B6-05DF-11D9-BA9E-00039351ED8A@physics.uc.edu> (raw)
In-Reply-To: <414627A4.4080109@codesourcery.com>


On Sep 13, 2004, at 4:05 PM, Mark Mitchell wrote:

>
> PR 15923
>
>   This is a testsuite regression on PowerPC, probably involving
>   varargs in some way.


Actually this is only on Darwin, it does not effect linux at all.
And it happens with structs smaller than 4 bytes passed through varargs,
see related bug 14262 which does have a patch which fixes the problem
but the patch was rejected by Jim for some reason, I cannot remember
why.

Thanks,
Andrew Pinski

  reply	other threads:[~2004-09-13 23:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14  0:30 Mark Mitchell
2004-09-14  1:14 ` Andrew Pinski [this message]
2004-09-14  1:28 ` Jan Hubicka
2004-09-14  5:02 ` Jeffrey A Law
2004-09-14  5:58   ` Mark Mitchell
2004-09-14  6:29     ` Jeffrey A Law
2004-09-14 15:54     ` Jan Hubicka
2004-09-14 17:07       ` Mark Mitchell
2004-09-14  6:28   ` Mark Mitchell
2004-09-15 21:25 ` Scott Robert Ladd
2004-09-16 21:58   ` Mark Mitchell
2004-09-16 15:58 ` GCC Status Report (2004-09-13) [--enable-mapped-location] Per Bothner
2004-09-16 18:45   ` Mark Mitchell
2004-09-16 18:56     ` Per Bothner
2004-09-16 19:02       ` Mark Mitchell
2004-09-16 19:03         ` Matt Austern
2004-09-16 19:31           ` Mark Mitchell
2004-09-16 22:50           ` Steven Bosscher
2004-09-16 19:28         ` Per Bothner
2004-09-16 19:46           ` Mark Mitchell
2004-09-14  4:48 GCC Status Report (2004-09-13) Wolfgang Bangerth
2004-09-18 11:02 Paolo Bonzini

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=D98B11B6-05DF-11D9-BA9E-00039351ED8A@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.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).