public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/10142: [Sparc] gcc -m64 produces wrong code when passing structures by value Date: Mon, 14 Apr 2003 17:26:00 -0000 [thread overview] Message-ID: <20030414172601.26213.qmail@sources.redhat.com> (raw) The following reply was made to PR c/10142; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: p.van-hoof@qub.ac.uk, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: c/10142: [Sparc] gcc -m64 produces wrong code when passing structures by value Date: Mon, 14 Apr 2003 19:22:49 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10142 This patch seems to fix the problem for me, but regtests are still in progress and I'm not completly sure what the test is supposed to do in the first place. Index: calls.c =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/calls.c,v retrieving revision 1.263 diff -u -r1.263 calls.c --- calls.c 14 Mar 2003 01:59:16 -0000 1.263 +++ calls.c 14 Apr 2003 17:20:36 -0000 @@ -1317,7 +1317,11 @@ it means that we are to pass this arg in the register(s) designated by the PARALLEL, but also to pass it in the stack. */ if (args[i].reg && GET_CODE (args[i].reg) == PARALLEL +#if 0 && XEXP (XVECEXP (args[i].reg, 0, 0), 0) == 0) +#else + ) +#endif args[i].pass_on_stack = 1; /* If this is an addressable type, we must preallocate the stack regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-04-14 17:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-14 17:26 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-22 15:06 ebotcazou
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=20030414172601.26213.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --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: linkBe 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).