public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/3711: ICE in instantiate_virtual_regs_1, at function.c:3880
Date: Tue, 26 Mar 2002 09:46:00 -0000	[thread overview]
Message-ID: <20020326174603.17295.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/3711; it has been noted by GNATS.

From: Richard Henderson <rth@redhat.com>
To: Nicola Pero <nicola@brainstorm.co.uk>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   GNUstep Developers <gnustep-dev@gnu.org>
Subject: Re: c/3711: ICE in instantiate_virtual_regs_1, at function.c:3880
Date: Tue, 26 Mar 2002 09:41:07 -0800

 On Tue, Mar 26, 2002 at 11:53:03AM +0000, Nicola Pero wrote:
 > Hmmm ... well this testcase arrives from a real example ... forwarding
 > code in some advanced OO stuff which worked perfectly well with all GCC
 > releases up to now (code from mframe.m in gnustep-base).
 
 No it didn't.  It worked perfectly well *with some particular abi*,
 which is not the same thing.
 
 > So I can use SMSmessages in place of a struct {char text[255];} everywhere
 > I want, but I can't pass it in place of a struct {char text[255];} to a
 > function ?
 
 Correct.
 
 > This is very confusing for users I must say.  And it is not how it worked
 > in previous versions of the compiler.
 
 Yes it is.  Like I said, this has *never* worked on sparc64, and
 never will.
 
 > I think you understood what the function in the testcase "wants/needs" to
 > do - which is that it can be called with an arbitrary struct (fixed size)
 > as the second argument, and it is informed of the size of the struct from
 > the first argument (which is just to say, a source providing the info at
 > runtime), and it needs to be able to access the bytes in the struct.
 
 Why don't you just pass a pointer to the structure all the time?
 
 
 r~


             reply	other threads:[~2002-03-26 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26  9:46 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25 23:14 rth
2002-03-28  9:26 Richard Henderson
2002-03-28  7:06 Nicola Pero
2002-03-26  3:56 Nicola Pero
2002-03-25 16:26 Richard Henderson

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=20020326174603.17295.qmail@sources.redhat.com \
    --to=rth@redhat.com \
    --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: 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).