public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Diego Novillo <dnovillo@google.com>
Subject: Re: [PATCH] Merge from LTO: eh_personality changes
Date: Thu, 10 Sep 2009 16:12:00 -0000	[thread overview]
Message-ID: <4AA9257F.60809@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909101757340.28140@zhemvz.fhfr.qr>

On 09/10/2009 09:02 AM, Richard Guenther wrote:
> It doesn't seem to work - I get ICEs in
>
>
> #2  0x00000000006d897b in output_addr_const (file=0x163c040,
> x=0x2aaaacaa5c80)
>      at /space/rguenther/src/svn/trunk/gcc/final.c:3619
> 3619          output_operand_lossage ("invalid expression as operand");
>
> (gdb) call debug_rtx (x)
> (mem:QI (symbol_ref:DI ("__gcc_personality_v0") [flags 0x41]) [0 S1 A8])
>
> #3  0x000000000064d3fd in dwarf2out_do_cfi_startproc (second=0 '\000')
>      at /space/rguenther/src/svn/trunk/gcc/dwarf2out.c:3851
> 3851          output_addr_const (asm_out_file, ref);

You have to drop the MEM, of course, i.e.

   return XEXP (DECL_RTL (decl), 0);

Also ideally, we'd give a proper prototype for the personality function. 
  Getting the struct and enum parameters right would be neigh impossible 
of course, but we could at least give it

   int personality(int, int, unsigned long long, void*, void*)


r~

  parent reply	other threads:[~2009-09-10 16:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 13:34 Richard Guenther
2009-09-04 13:37 ` Diego Novillo
2009-09-04 13:41   ` Richard Guenther
2009-09-05 16:37 ` Richard Henderson
2009-09-05 16:38 ` Richard Henderson
2009-09-05 17:24   ` Richard Guenther
2009-09-05 18:11     ` Richard Henderson
2009-09-08 12:37       ` Richard Guenther
2009-09-08 15:20         ` Richard Guenther
2009-09-08 15:49           ` Richard Henderson
2009-09-10 13:12             ` Richard Guenther
2009-09-10 14:37               ` Richard Guenther
2009-09-10 14:52                 ` Richard Guenther
2009-09-10 15:50                   ` Richard Guenther
2009-09-10 15:57                     ` Richard Henderson
2009-09-10 15:50                   ` Richard Henderson
2009-09-10 16:02                     ` Richard Guenther
2009-09-10 16:06                       ` Richard Guenther
2009-09-10 16:23                         ` Richard Henderson
2009-09-11 13:25                           ` Richard Guenther
2009-09-11 15:41                             ` Richard Henderson
2009-09-11 16:41                               ` Richard Guenther
2009-09-11 17:05                                 ` Richard Henderson
2009-09-13 22:57                                 ` H.J. Lu
2010-12-29  5:30                                   ` H.J. Lu
2010-12-29  5:36                                     ` H.J. Lu
2011-02-08  2:06                                       ` H.J. Lu
2009-09-10 16:12                       ` Richard Henderson [this message]
2009-09-08 17:38           ` Eric Botcazou
2009-09-08 15:48         ` Richard Henderson
2009-09-08 16:04           ` Richard Guenther
2009-09-09  9:34             ` Richard Guenther
2009-09-09 15:24               ` Richard Henderson
2009-09-09 15:26                 ` Richard Guenther
2009-09-14  2:43 David Edelsohn
2009-09-14  5:38 ` Gerald Pfeifer
2009-09-14  9:37 ` Richard Guenther
2009-09-15  8:15   ` Gerald Pfeifer
2009-09-15 11:48     ` David Edelsohn

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=4AA9257F.60809@redhat.com \
    --to=rth@redhat.com \
    --cc=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.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).