From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>,
Jakub Jelinek <jakub@redhat.com>, Tom de Vries <tdevries@suse.de>,
Ian Lance Taylor <ian@airs.com>
Cc: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: UNSPEC related notes and libbacktrace
Date: Wed, 23 Jan 2019 09:29:00 -0000 [thread overview]
Message-ID: <4de39b2d-5a0c-5b05-5d1b-ca349868b74a@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.21.1901210156340.5414@anthias.pfeifer.com>
On 1/22/19 10:50 AM, Gerald Pfeifer wrote:
> I've been seeing the following in my testsuite runs which I didn't
> get a month or so ago. Are these due to your changes, Jakub, or
> some changes around libbacktrace?
I can confirm that and I've just created a PR for it:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89006
Martin
prev parent reply other threads:[~2019-01-23 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 9:49 [PATCH] Silence some dwarf2out UNSPEC related notes (PR debug/88723) Jakub Jelinek
2019-01-07 9:50 ` Richard Biener
2019-01-22 9:50 ` UNSPEC related notes and libbacktrace (was: [PATCH] Silence some dwarf2out UNSPEC related notes (PR debug/88723)) Gerald Pfeifer
2019-01-23 9:29 ` Martin Liška [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=4de39b2d-5a0c-5b05-5d1b-ca349868b74a@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ian@airs.com \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=tdevries@suse.de \
/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).