public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94129] Using almost any openacc !$acc directive causes ICE "compressed stream: data error"
Date: Thu, 16 Apr 2020 13:14:46 +0000	[thread overview]
Message-ID: <bug-94129-4-cfZReeWH1T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94129-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94129

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #9)
> (In reply to Martin Liška from comment #8)
> > @Richi: Can you please enable zstd for our nvptx cross compiler:
> > 
> > $ x86_64-suse-linux-accel-nvptx-none-gcc-10 -v
> > ...
> > Supported LTO compression algorithms: zlib
> > 
> > We'll need to add
> > BuildRequires: libzstd-devel
> > 
> > into cross spec file.
> 
> @Richi: PING

done

  parent reply	other threads:[~2020-04-16 13:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 19:49 [Bug fortran/94129] New: " andrew at blamsoft dot com
2020-03-11  7:45 ` [Bug fortran/94129] " rguenth at gcc dot gnu.org
2020-03-11  8:28 ` marxin at gcc dot gnu.org
2020-03-11 12:57 ` doko at debian dot org
2020-03-11 13:07 ` rguenth at gcc dot gnu.org
2020-03-11 13:11 ` rguenth at gcc dot gnu.org
2020-03-11 13:13 ` marxin at gcc dot gnu.org
2020-03-11 15:34 ` doko at debian dot org
2020-03-12 15:22 ` marxin at gcc dot gnu.org
2020-04-16 13:02 ` marxin at gcc dot gnu.org
2020-04-16 13:14 ` rguenth at gcc dot gnu.org [this message]
2020-04-17  8:46 ` marxin at gcc dot gnu.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=bug-94129-4-cfZReeWH1T@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).