public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34999] Fallthru crossing edges in partition_hot_cold_basic_blocks are not been fixed when the section ends with call insn
Date: Fri, 29 Feb 2008 08:57:00 -0000	[thread overview]
Message-ID: <20080229085616.31160.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34999-13229@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from jakub at gcc dot gnu dot org  2008-02-29 08:56 -------
.LSFDE3:
        .long   .LEFDE3-.LASFDE3        # FDE Length
.LASFDE3:
        .long   .LASFDE3-.Lframe1       # FDE CIE offset
        .long   .LHOTB2 # FDE initial location
        .long   .LHOTE2-.LHOTB2 # FDE address range
        .long   .LCOLDB2        # FDE initial location
        .long   .LCOLDE2-.LCOLDB2       # FDE address range
        .uleb128 0x0    # Augmentation size
        .byte   0x4     # DW_CFA_advance_loc4
        .long   .LCFI2-.LFB3
        .byte   0xe     # DW_CFA_def_cfa_offset
        .uleb128 0x10
        .byte   0x86    # DW_CFA_offset, column 0x6
        .uleb128 0x2
        .byte   0x4     # DW_CFA_advance_loc4
        .long   .LCFI3-.LCFI2
        .byte   0xd     # DW_CFA_def_cfa_register
        .uleb128 0x6
        .align 8
.LEFDE3:

is not a valid .eh_frame FDE, the
2005-03-31  Caroline Tice  <ctice@apple.com>

        (output_call_frame_info): Add test to see if function switches text
        sections in the middle; if so, use appropriate extra hot and cold
        section labels to compute size deltas for the hot and cold sections.

change was totally broken.  There is no such thing as a two ranges FDE in
Dwarf2/3.  FDE starts with FDE length, CIE offset, FDE initial location, FDE
address range, depending on CIE optionally with augmentation size and
augmentation and then CFA instructions.  So, to describe .text/.text.unlikely
split function, you need two FDEs, one describing the .text section, the other
describing .text.unlikely section.  When the code jumps in between the
sections, you need to insert CFA instructions that reflect what really changed.
The easiest would be to use .cfi_* assembler directives that recentish gas
supports and emitting them inline in the code, rather than creating separate
.eh_frame.  But I believe we need some more help from gas - particularly more
powerful .cfi_escape and some easy way to just save current state resp. restore
it.  That way you could save the state at the jump location and restore it at
the jump target and let gas compute what CFA instructions are needed.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34999


  parent reply	other threads:[~2008-02-29  8:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 16:20 [Bug rtl-optimization/34999] New: " eres at il dot ibm dot com
2008-01-28 16:28 ` [Bug rtl-optimization/34999] " eres at il dot ibm dot com
2008-01-29 17:12 ` eres at il dot ibm dot com
2008-02-27 13:29 ` revitale at gcc dot gnu dot org
2008-02-28  9:48 ` ubizjak at gmail dot com
2008-02-28 13:01 ` eres at il dot ibm dot com
2008-02-28 13:27 ` ubizjak at gmail dot com
2008-02-28 13:50 ` eres at il dot ibm dot com
2008-02-28 18:35 ` ubizjak at gmail dot com
2008-02-28 19:13 ` ubizjak at gmail dot com
2008-02-29  5:23 ` eres at il dot ibm dot com
2008-02-29  5:54 ` hjl dot tools at gmail dot com
2008-02-29  6:08 ` ubizjak at gmail dot com
2008-02-29  6:33 ` ubizjak at gmail dot com
2008-02-29  6:48 ` ubizjak at gmail dot com
2008-02-29  8:57 ` jakub at gcc dot gnu dot org [this message]
2008-03-04 14:51 ` uweigand at gcc dot gnu dot org
2008-03-04 15:10 ` jakub at gcc dot gnu dot org
2008-03-16 16:28 ` danglin at gcc dot gnu dot org
2008-04-08 11:07 ` eres at il dot ibm dot com
2008-04-08 11:14 ` jakub at gcc dot gnu dot org
2008-12-29  2:41 ` pinskia at gcc dot gnu dot org
2009-03-27 16:37 ` ghazi at gcc dot gnu dot org
2009-03-27 17:27 ` steven at gcc dot gnu dot org
2009-07-24 15:37 ` [Bug rtl-optimization/34999] Incorrect FDE entries with hot/cold code section splitting (partition_hot_cold_basic_blocks) jakub at gcc dot gnu dot org
2009-07-24 23:31 ` jakub at gcc dot gnu dot org
2009-08-06 19:54 ` ghazi at gcc dot gnu dot org
2009-09-07  1:04 ` ghazi at gcc dot gnu dot org
2009-12-01 15:14 ` ghazi at gcc dot gnu dot org
2009-12-01 15:16 ` rguenth at gcc dot gnu dot org

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=20080229085616.31160.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).