public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "breggen at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/12354] compiling glibc gives "previous cfi entry not closed" while compiling on ARM
Date: Wed, 05 Jan 2011 21:13:00 -0000	[thread overview]
Message-ID: <bug-12354-131-lNx4OeMlR2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12354-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12354

--- Comment #3 from michel van der breggen <breggen at hotmail dot com> 2011-01-05 21:12:57 UTC ---
I've been digging around in the created .s file and found that it indeed does
not create correct cfi information. At some point cfi information is placed
without actually setting an cfi_startproc or no cfi_endproc is included. 

What I think is that the implementation of cfi commands for the ARM is not
completely implemented correctly because in DOARGS and UNDOARGS ( in
/sysdeps/unix/sysv/linux/arm/sysdep.h ) no check is made of the cfi is indeed
within start-end pattern.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2011-01-05 21:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12354-131@http.sourceware.org/bugzilla/>
2011-01-05 21:13 ` breggen at hotmail dot com [this message]
2011-01-05 21:59 ` joseph at codesourcery dot com
2011-09-08  0:22 ` r.berber at computer dot org
2011-09-08 18:27 ` napadovskiy at gmail dot com
2011-09-08 20:33 ` r.berber at computer dot org
2011-09-08 23:28 ` r.berber at computer dot org
2012-01-03  0:38 ` vapier at gentoo dot org
2012-01-09 19:05 ` vapier at gentoo dot org
2014-02-16 18:23 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-05-28 19:46 ` schwab at sourceware dot org
2014-06-27 14:04 ` fweimer at redhat 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=bug-12354-131-lNx4OeMlR2@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).