public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/45103] DW_OP_reg* has too large valid range for noreturn funcs Date: Wed, 28 Jul 2010 09:55:00 -0000 [thread overview] Message-ID: <20100728095452.31174.qmail@sourceware.org> (raw) In-Reply-To: <bug-45103-12292@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from jan dot kratochvil at redhat dot com 2010-07-28 09:54 ------- Created an attachment (id=21331) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21331&action=view) .s files for x86_64-unknown-linux-gnu. GDB bug (probably invalid): http://sourceware.org/bugzilla/show_bug.cgi?id=11838 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45103
next prev parent reply other threads:[~2010-07-28 9:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-28 9:54 [Bug debug/45103] New: " jan dot kratochvil at redhat dot com 2010-07-28 9:55 ` jan dot kratochvil at redhat dot com [this message] 2010-07-28 10:03 ` [Bug debug/45103] " jakub at gcc dot gnu dot org 2010-07-28 17:00 ` jakub at gcc dot gnu dot org 2010-09-07 22:46 ` jakub 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=20100728095452.31174.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: linkBe 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).