public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Lokesh Janghel <lokeshjanghel91@gmail.com>,
	umesh.kalappa0@gmail.com,        richard.guenther@gmail.com,
	gcc-patches@gcc.gnu.org,        Uros Bizjak <ubizjak@gmail.com>
Subject: Re: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626
Date: Sun, 06 Jan 2019 17:29:00 -0000	[thread overview]
Message-ID: <20190106172941.GL30353@tucnak> (raw)
In-Reply-To: <62d8bc46-335d-00ff-3412-59a4321288a7@suse.cz>

On Sun, Jan 06, 2019 at 06:25:35PM +0100, Martin Liška wrote:
> The patch causes failures in libffi:
> https://github.com/libffi/libffi/issues/463
> 
> Can you please take a look?

Perhaps PR88521?  A patch has been posted for that and even approved:
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01682.html
but not actually committed yet.

	Jakub

  reply	other threads:[~2019-01-06 17:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  9:02 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa
2018-11-15 10:24 ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85667 Umesh Kalappa
2018-11-15 10:32 ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Richard Biener
2018-11-16  8:07   ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa
2018-11-16  9:08     ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Richard Biener
2018-11-16 10:51       ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa
2018-11-16 11:27         ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Jakub Jelinek
     [not found]           ` <CACcU4_r4GESOudiV+4FYq9Drg3kJuCdyVVpvnTTqV=Y-=xoDjQ@mail.gmail.com>
2018-11-19 10:38             ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Lokesh Janghel
2018-11-20  9:33               ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Jakub Jelinek
2018-11-21 12:36                 ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa
2018-11-21 13:07                   ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Jakub Jelinek
2018-11-21 13:25                     ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa
2018-11-26 21:46                       ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Jeff Law
2019-01-06 17:25               ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Martin Liška
2019-01-06 17:29                 ` Jakub Jelinek [this message]
2018-11-20  6:59             ` https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87626 Umesh Kalappa

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=20190106172941.GL30353@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lokeshjanghel91@gmail.com \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.com \
    --cc=ubizjak@gmail.com \
    --cc=umesh.kalappa0@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).