public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jan Hubicka <hubicka@ucw.cz>, Richard Henderson <rth@redhat.com>,
	bernds@codesourcery.com, gcc-patches@gcc.gnu.org,
	tglek@mozilla.com
Subject: Re: [RFC PATCH 0/9] CFG aware dwarf2 cfi generation
Date: Thu, 04 Aug 2011 13:38:00 -0000	[thread overview]
Message-ID: <20110804133747.GC12248@kam.mff.cuni.cz> (raw)
In-Reply-To: <m2hb5y0yrv.fsf@firstfloor.org>

> Jan Hubicka <hubicka@ucw.cz> writes:
> >
> > Cool, will this also help to handle alternate entry points, so we can move ahead
> > on this area we got stuck years ago?  (i.e. add support for alternate entry points on
> > i386 skipping IP pointer load in PIC mode/using register passing conventions)
> 
> Also alternative entry points to skip x87 in favour of SSE 
> register passing for FP would be really nice.

Yep, there is quite some potential in this on x86. On x86-64 also stack
alignment prologues could be eliminated.

I guess the PIC tricks could do wonders for Mozilla. Additionally once this
works, we can move ahead with alternate entry points at gimple level possibly
re-implementing thunks/ctor clonning using them.

So if we finally get past the unwind info issues, I could start poking about
getting the PIC codegen working as a first experiment.

Honza
> 
> -Andi
> 
> -- 
> ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2011-08-04 13:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 23:10 Richard Henderson
2011-07-14 23:10 ` [PATCH 6/9] dwarf2cfi: Convert queued_reg_save to a VEC Richard Henderson
2011-07-14 23:10 ` [PATCH 3/9] dwarf2cfi: Populate CUR_ROW->REG_SAVE Richard Henderson
2011-07-14 23:10 ` [PATCH 1/9] dwarf2cfi: Introduce a dw_cfi_row state Richard Henderson
2011-07-14 23:10 ` [PATCH 8/9] dwarf2cfi: Introduce dw_trace_info Richard Henderson
2011-07-14 23:10 ` [PATCH 4/9] dwarf2cfi: Implement change_cfi_row Richard Henderson
2011-07-14 23:10 ` [PATCH 2/9] dwarf2cfi: Rename cfi_insn to add_cfi_insn Richard Henderson
2011-07-14 23:16 ` [PATCH 9/9] dwarf2cfi: Generate and connect traces Richard Henderson
2011-08-06 17:46   ` H.J. Lu
2011-07-14 23:25 ` [PATCH 7/9] dwarf2cfi: Allocate reg_saved_in_data in the heap Richard Henderson
2011-07-15  6:09 ` [PATCH 5/9] dwarf2cfi: Remove dw_cfi_row_ref typedef Richard Henderson
2011-07-15 23:21 ` [RFC PATCH 0/9] CFG aware dwarf2 cfi generation Richard Henderson
2011-07-16  4:09   ` Bernd Schmidt
2011-07-16  6:07     ` Richard Henderson
2011-07-24  8:23 ` Richard Henderson
2011-07-24  8:24   ` Bernd Schmidt
2011-08-03 20:24   ` Jan Hubicka
2011-08-03 20:26     ` Richard Henderson
2011-08-03 20:33       ` Jan Hubicka
2011-08-04  1:08     ` Andi Kleen
2011-08-04 13:38       ` Jan Hubicka [this message]
2011-07-25  3:15 David Edelsohn
2011-07-25  8:46 ` Richard Henderson
2011-07-25 14:23   ` 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=20110804133747.GC12248@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=andi@firstfloor.org \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.com \
    --cc=tglek@mozilla.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).