public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gang.chen.5i5j at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54694] [4.7/4.8 Regression] internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2out.c:2387
Date: Sat, 05 Sep 2015 02:49:00 -0000 [thread overview]
Message-ID: <bug-54694-4-q0T1PyRj2I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54694-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54694
Chen Gang <gang.chen.5i5j at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gang.chen.5i5j at gmail dot com
--- Comment #25 from Chen Gang <gang.chen.5i5j at gmail dot com> ---
(In reply to Richard Henderson from comment #20)
> Author: rth
> Date: Thu Jan 16 16:33:30 2014
> New Revision: 206667
>
> URL: http://gcc.gnu.org/viewcvs?rev=206667&root=gcc&view=rev
> Log:
> PR debug/54694
>
> Diagnose frame_pointer_required vs fixed hfp
>
> Added:
> branches/gcc-4_7-branch/gcc/testsuite/gcc.target/i386/pr54694.c
> Modified:
> branches/gcc-4_7-branch/gcc/ChangeLog
> branches/gcc-4_7-branch/gcc/ira.c
> branches/gcc-4_7-branch/gcc/reginfo.c
> branches/gcc-4_7-branch/gcc/rtl.h
After this git commit, the current blackfin kernel code can not pass building
when enable FUNCTION_TRACER. The related bug number is Bug65804
I want to consult: Is it the original gcc and current kernel issue? or our
related git commit "e52beba PR debug/54694" need be improved?
Thanks.
prev parent reply other threads:[~2015-09-05 2:49 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
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 [this message]
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-q0T1PyRj2I@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).