public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59617] [vectorizer] ICE in vectorizable_mask_load_store with AVX-512F's gathers enabled.
Date: Thu, 03 Apr 2014 13:31:00 -0000	[thread overview]
Message-ID: <bug-59617-4-wCcOOE1g0Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59617-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59617

--- Comment #19 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #17)
> (In reply to Iain Sandoe from comment #14)
> > (In reply to Dominique d'Humieres from comment #13)
> > > Another option would be to add -std=c99 for darwin.
> > 
> > I would suggest that this is the Right Thing to do.
> 
> There is quite some usage of __restrict in gcc.target/i386/ directory. Why
> doesn't this problem trigger with e.g. avx2-gather-4.c, which also uses
> __restrict?

presumably, other tests don't include the system header that is the source of
the problem (which can be checked).

My understanding is that restrict is c99 (and, the addition of  -std= was only
being proposed for darwin, so other targets would be unaffected)

however, that said, I am of course open to other solutions.
>From gcc-bugs-return-448201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 03 13:41:31 2014
Return-Path: <gcc-bugs-return-448201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1425 invoked by alias); 3 Apr 2014 13:41:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1375 invoked by uid 48); 3 Apr 2014 13:41:26 -0000
From: "tim.moloney at mrsl dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60731] [4.7/4.8/4.9 Regression] dynamic library not getting reinitialized on multiple calls to dlopen()
Date: Thu, 03 Apr 2014 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.moloney at mrsl dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60731-4-tErJrReMzh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-04/txt/msg00221.txt.bz2
Content-length: 202

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`731

--- Comment #6 from Tim Moloney <tim.moloney at mrsl dot com> ---
I created glibc bug #16805
(https://sourceware.org/bugzilla/show_bug.cgi?id\x16805).


  parent reply	other threads:[~2014-04-03 13:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 22:21 [Bug tree-optimization/59617] New: " kirill.yukhin at intel dot com
2014-01-13 19:17 ` [Bug tree-optimization/59617] " jakub at gcc dot gnu.org
2014-01-29 17:35 ` kyukhin at gcc dot gnu.org
2014-03-30 19:06 ` dominiq at lps dot ens.fr
2014-04-02  7:52 ` ubizjak at gmail dot com
2014-04-03  8:50 ` dominiq at lps dot ens.fr
2014-04-03  9:55 ` dominiq at lps dot ens.fr
2014-04-03 11:38 ` dominiq at lps dot ens.fr
2014-04-03 11:42 ` kirill.yukhin at intel dot com
2014-04-03 11:54 ` dominiq at lps dot ens.fr
2014-04-03 12:00 ` dominiq at lps dot ens.fr
2014-04-03 13:19 ` dominiq at lps dot ens.fr
2014-04-03 13:23 ` kirill.yukhin at intel dot com
2014-04-03 13:30 ` dominiq at lps dot ens.fr
2014-04-03 13:31 ` iains at gcc dot gnu.org [this message]
2020-09-14 12:48 ` rguenth 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-59617-4-wCcOOE1g0Z@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).