public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54694] [4.7/4.8/4.9 Regression] internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2out.c:2387
Date: Mon, 13 Jan 2014 19:32:00 -0000	[thread overview]
Message-ID: <bug-54694-4-os1FoAQJpj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54694-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Richard Henderson <rth at gcc dot gnu.org> ---
I'm tempted to simply say this is user-error.  It's the use of the global
register of EBP that's causing the problem.  And honestly I don't see a
way around it.

The only possible resolution I could see is to generate an error or sorry
earlier, before the ICE.  But it still wouldn't let the test case compile.

Anyway that's exactly why current QEMU does not do this anymore.  So one
can also fix the "problem" by upgrading from qemu-kvm-1.1 to qemu-1.7.


  parent reply	other threads:[~2014-01-13 19:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 21:10 [Bug preprocessor/54694] New: " toralf.foerster at gmx dot de
2012-09-25  7:34 ` [Bug preprocessor/54694] " rguenth at gcc dot gnu.org
2012-09-25 15:27 ` toralf.foerster at gmx dot de
2012-09-26  9:10 ` rguenth at gcc dot gnu.org
2012-09-26 17:19 ` toralf.foerster at gmx dot de
2012-09-26 17:59 ` markus at trippelsdorf dot de
2013-01-03 19:35 ` toralf.foerster at gmx dot de
2013-11-16 21:46 ` valentin.ilie at gmail dot com
2013-11-28 11:45 ` octoploid at yandex dot com
2013-11-28 12:08 ` [Bug debug/54694] [4.7/4.8/4.9 Regression] " Joost.VandeVondele at mat dot ethz.ch
2013-11-28 12:15 ` hjl.tools at gmail dot com
2013-11-28 12:17 ` hjl.tools at gmail dot com
2013-12-19 15:19 ` rguenth at gcc dot gnu.org
2014-01-10 19:17 ` ubizjak at gmail dot com
2014-01-10 19:26 ` hjl.tools at gmail dot com
2014-01-13 19:32 ` rth at gcc dot gnu.org [this message]
2014-01-13 19:42 ` toralf.foerster at gmx dot de
2014-01-15 21:41 ` rth at gcc dot gnu.org
2014-01-15 21:47 ` [Bug debug/54694] [4.7/4.8 " rth at gcc dot gnu.org
2014-01-16 16:24 ` rth at gcc dot gnu.org
2014-01-16 16:34 ` rth at gcc dot gnu.org
2014-01-16 16:35 ` rth at gcc dot gnu.org
2014-01-16 19:16 ` jakub at gcc dot gnu.org
2014-01-16 19:21 ` jakub at gcc dot gnu.org
2014-01-16 19:22 ` jakub at gcc dot gnu.org
2015-09-05  2:49 ` gang.chen.5i5j at gmail 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-54694-4-os1FoAQJpj@http.gcc.gnu.org/bugzilla/ \
    --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).