public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/66275] __attribute__((sysv_abi)) with x86_64-w64-mingw32-gcc generates incorrect code
Date: Tue, 26 May 2015 11:09:00 -0000	[thread overview]
Message-ID: <bug-66275-4-6JAEAvDm4L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66275-4@http.gcc.gnu.org/bugzilla/>

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

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|x86_64-w64-mingw32          |

--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
This is RTL infrastructure problem, not target specific.
>From gcc-bugs-return-487279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 26 11:10:13 2015
Return-Path: <gcc-bugs-return-487279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24413 invoked by alias); 26 May 2015 11:10:12 -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 24058 invoked by uid 48); 26 May 2015 11:09:54 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66288] parallelized loop vectorized with runtime alias check
Date: Tue, 26 May 2015 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66288-4-5dtiPYpFbV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66288-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66288-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: 2015-05/txt/msg02119.txt.bz2
Content-length: 467

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf288

--- Comment #2 from vries at gcc dot gnu.org ---
Before parallelization, we have:
...
  doubleD.32 dataD.1837[1000];
  doubleD.32 resultsD.1836[1000];

  ...

  # VUSE <.MEM_19>
  _6 = dataD.1837[idx_18];
  _7 = _6 * 1.2199999999999999289457264239899814128875732421875e+1;
  # .MEM_8 = VDEF <.MEM_19>
  resultsD.1836[idx_18] = _7;
...

We could annotate these memory references with dependence clique information.


  parent reply	other threads:[~2015-05-26 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 15:27 [Bug c/66275] New: " peter at cordes dot ca
2015-05-25  9:58 ` [Bug rtl-optimization/66275] " ubizjak at gmail dot com
2015-05-26 10:46 ` rguenth at gcc dot gnu.org
2015-05-26 11:09 ` ubizjak at gmail dot com [this message]
2015-06-01 19:52 ` [Bug target/66275] " ubizjak at gmail dot com
2015-06-03 15:47 ` uros at gcc dot gnu.org
2015-06-08 18:42 ` uros at gcc dot gnu.org
2015-06-08 20:07 ` uros at gcc dot gnu.org
2015-06-08 20:59 ` uros at gcc dot gnu.org
2015-06-08 21:01 ` ubizjak at gmail dot com

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-66275-4-6JAEAvDm4L@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).