public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: gcc-gnats@gcc.gnu.org
Subject: middle-end/3544: SJLJ exceptions with dwarf2 debug broken
Date: Tue, 03 Jul 2001 07:16:00 -0000	[thread overview]
Message-ID: <200107031405.PAA26426@sun18.cambridge.arm.com> (raw)

>Number:         3544
>Category:       middle-end
>Synopsis:       SJLJ exceptions with dwarf2 debug broken
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 03 07:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Richard Earnshaw
>Release:        3.0
>Organization:
>Environment:
System: SunOS sun18 5.7 Generic_106541-11 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4

	
host: sparc-sun-solaris2.7
build: sparc-sun-solaris2.7
target: arm-unknown-elf
configured with: /home/rearnsha/thirdparty/gcc/configure --prefix=/home/rearnsha/thirdparty/install --target=arm-elf --with-headers=/home/rearnsha/thirdparty/utils/newlib/libc/include --enable-languages=c,c++,objc,f77
>Description:
	Building libstdc++-v3 with an arm-elf cross compiler generates object 
	files that reference non-existent internal labels from the unwind 
	information tables.  This seems to be occuring because dwarf2out.c
	and except.c maintain distinct counters for the funcdef number and
	that these are getting out of step.

	In dwarf2out (dwarf2out_begin_prologue) we have:
		fde->funcdef_number = current_funcdef_number;

	and (output_call_frame_info) has:
	          ASM_GENERATE_INTERNAL_LABEL (l1, "LLSDA",
					       fde->funcdef_number);

	but in except.c (output_function_exception_table) we have

		if (! cfun->uses_eh_lsda)
		  return;

		funcdef_number = (USING_SJLJ_EXCEPTIONS
		    ? sjlj_funcdef_number
		    : current_funcdef_number);
		...
		ASM_OUTPUT_INTERNAL_LABEL (asm_out_file, "LLSDA",
					   funcdef_number);

	hence the generated label and the fde->funcdef_number can get out
	of step if not all functions use lsda information.

	
	
>How-To-Repeat:
	Build libstdc++-v3/libsupc++/eh_aux_runtime.cc for arm-unknown-elf
	with the gcc-3.0 release.  Note that the resulting object file 
	defines the labels LSDA0 & LSDA1, but that the exception unwind
	table references LSDA1 and LSDA2.  The resulting object file will
	fail to link.
	
>Fix:
	No idea.
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-03  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03  7:16 Richard Earnshaw [this message]
2002-06-17  2:46 rth
2002-06-17 11:26 rth
2002-06-24  6:06 Richard Earnshaw
2003-01-14 23:13 bangerth
2003-01-15  9:56 Richard Earnshaw
2003-01-15 14:56 Wolfgang Bangerth

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=200107031405.PAA26426@sun18.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=gcc-gnats@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).