public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/40521] [4.4/4.5 Regression] -g causes GCC to generate .eh_frame
Date: Fri, 09 Oct 2009 18:28:00 -0000	[thread overview]
Message-ID: <20091009182808.23579.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40521-3264@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from mikpe at it dot uu dot se  2009-10-09 18:28 -------
I've been testing a backport of Jakub's patch to gcc-4.4, but it breaks
bootstrap on i686-linux with binutils-2.18.50.0.6 (Fedora 9) because stage1 gcc
outputs .cfi_sections directives even though the assembler doesn't support
them.
Current gcc-4.5 bootstraps Ok on the same machine.

The configure test correctly detects that cfi sections don't work with this as,
and records that with "#define HAVE_GAS_CFI_SECTIONS_DIRECTIVE 0".

In gcc-4.5 dwarf2out_do_cfi_asm() returns true. The code in dwarf2out_init()
inside #ifdef HAVE_GAS_CFI_SECTIONS_DIRECTIVE finds that USING_SJLJ_EXCEPTIONS
is false and !flag_exceptions is also false, so the call to emit a
.cfi_sections directive is not made. (!flag_unwind_tables varies, but it does
not matter since it's && with !flag_exceptions which always is false.)

In gcc-4.4 dwarf2out_do_cfi_asm() also returns true. The code in
dwarf2out_init() finds that USING_SJLJ_EXCEPTIONS is false but both
!flag_unwind_tables and !flag_exceptions are true, so a .cfi_sections directive
is emitted, causing the assembler to signal an error.

One thing that I find strange is that dwarf2out_do_cfi_asm() unconditionally
tests HAVE_GAS_CFI_SECTIONS_DIRECTIVE in an "if (!...)", which works since that
symbol is #defined as 0 or 1, while dwarf2out_init() instead has an #ifdef
HAVE_GAS_CFI_SECTIONS_DIRECTIVE around the conditional output of the directive.
Shouldn't that #ifdef be an #if?


-- 


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


  parent reply	other threads:[~2009-10-09 18:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 15:17 [Bug debug/40521] New: " drow at gcc dot gnu dot org
2009-06-22 15:20 ` [Bug debug/40521] " drow at gcc dot gnu dot org
2009-06-22 15:23 ` drow at gcc dot gnu dot org
2009-06-23  9:33 ` rguenth at gcc dot gnu dot org
2009-06-23 11:10 ` jakub at gcc dot gnu dot org
2009-06-23 12:24 ` drow at gcc dot gnu dot org
2009-07-22 10:33 ` jakub at gcc dot gnu dot org
2009-07-29 22:38 ` jsm28 at gcc dot gnu dot org
2009-10-01 15:45 ` jakub at gcc dot gnu dot org
2009-10-02 18:52 ` jakub at gcc dot gnu dot org
2009-10-08 15:18 ` doko at ubuntu dot com
2009-10-08 15:37 ` ramana at gcc dot gnu dot org
2009-10-09 18:28 ` mikpe at it dot uu dot se [this message]
2009-10-09 18:55 ` jakub at gcc dot gnu dot org
2009-10-09 19:07 ` jakub at gcc dot gnu dot org
2009-10-09 19:17 ` jakub at gcc dot gnu dot org
2009-10-09 19:51 ` mikpe at it dot uu dot se
2009-10-11 22:52 ` f dot frumento at ngi dot it
2009-10-12 11:36 ` sebastian dot huber at embedded-brains dot de
2009-10-12 12:34 ` mikpe at it dot uu dot se
2009-10-12 12:35 ` jakub at gcc dot gnu dot org
2009-10-13 12:53 ` mikpe at it dot uu dot se
2009-10-16 14:55 ` jakub at gcc dot gnu dot org
2009-10-16 17:35 ` ebotcazou at gcc dot gnu dot org
2009-10-17  7:28 ` jakub at gcc dot gnu dot org
2009-10-19 12:16 ` jakub at gcc dot gnu dot org
2009-10-19 12:21 ` jakub at gcc dot gnu dot org
2009-10-21 10:48 ` mikpe at it dot uu dot se
2010-03-31 15:50 ` tschwinge at gcc dot gnu dot org
     [not found] <bug-40521-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:15 ` jackie.rosen at hushmail dot com

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=20091009182808.23579.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).