From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Jason Merrill <jason@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [debug-early] reuse variable DIEs and fix their context
Date: Thu, 04 Sep 2014 19:42:00 -0000 [thread overview]
Message-ID: <20140904194237.GC12042@lug-owl.de> (raw)
In-Reply-To: <5408B0D1.7010708@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Thu, 2014-09-04 11:34:57 -0700, Aldy Hernandez <aldyh@redhat.com> wrote:
> On 09/04/14 11:23, Richard Biener wrote:
> > On September 4, 2014 7:54:14 PM CEST, Aldy Hernandez <aldyh@redhat.com> wrote:
> > > > I think this merge caused bootstrap failure on Linux/i686
> > > > https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00010.html
> > > I incorrectly pushed my branch onto trunk. It's being reverted.
> >
> > Too bad!
>
> Hey, I tried to sneak in all my changes onto trunk...but people
> noticed too fast. It's those Ada people! I should've added fixed
> the debugging hooks for their language :).
The sh4/sh64 folks would have noticed, too:
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350741
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350742
:)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: 17:45 <@Eimann> Hrm, das E90 hat keinen Lebenszeit Call-Time Counter mehr
the second : 17:46 <@jbglaw> Eimann: Wofür braucht man das?
17:46 <@jbglaw> Eimann: Für mich ist an 'nem Handy wichtig, daß ich mein
Gegeüber hören kann. Und daß mein Gegenüber mich versteht...
17:47 <@KrisK> jbglaw: was du meinst ist wodka.
17:47 <@KrisK> jbglaw: es klingelt und man hört stimmen
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-09-04 19:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 2:43 Aldy Hernandez
2014-08-28 13:58 ` Richard Biener
2014-08-28 17:35 ` Aldy Hernandez
2014-08-28 18:01 ` Jason Merrill
2014-08-28 19:13 ` Richard Biener
2014-08-28 20:14 ` Jason Merrill
2014-08-29 9:09 ` Richard Biener
2014-09-03 17:55 ` Aldy Hernandez
2014-09-04 10:42 ` Richard Biener
2014-09-05 2:38 ` Aldy Hernandez
2014-09-05 9:00 ` Richard Biener
2014-09-09 0:01 ` Aldy Hernandez
2014-09-09 9:16 ` Richard Biener
2014-09-12 0:51 ` Aldy Hernandez
2014-09-12 8:13 ` Richard Biener
2014-09-12 15:15 ` Jason Merrill
2014-09-12 17:11 ` Aldy Hernandez
2014-09-12 17:33 ` Jason Merrill
2014-09-12 17:48 ` Aldy Hernandez
2014-09-12 17:56 ` Jason Merrill
2014-09-16 15:49 ` Aldy Hernandez
2014-09-15 9:32 ` Richard Biener
2014-09-15 18:46 ` Jason Merrill
2014-12-18 19:26 ` Aldy Hernandez
2014-12-19 11:20 ` Richard Biener
2014-12-19 18:58 ` Jan Hubicka
2014-12-19 19:01 ` Jan Hubicka
2014-12-19 19:02 ` Aldy Hernandez
2014-12-19 19:31 ` Jason Merrill
2014-12-19 19:50 ` Jan Hubicka
2014-12-20 10:09 ` Aldy Hernandez
2015-01-08 12:24 ` Richard Biener
2014-12-19 19:03 ` Aldy Hernandez
2014-09-04 17:53 ` H.J. Lu
2014-09-04 17:54 ` Aldy Hernandez
2014-09-04 18:23 ` Richard Biener
2014-09-04 18:35 ` Aldy Hernandez
2014-09-04 18:38 ` Christophe Lyon
2014-09-04 19:42 ` Jan-Benedict Glaw [this message]
2015-01-08 15:20 Aldy Hernandez
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=20140904194237.GC12042@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jason@redhat.com \
--cc=richard.guenther@gmail.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).