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 target/59021] [4.9 regression] new vzeroupper instructions generated with -mavx
Date: Wed, 06 Nov 2013 17:28:00 -0000	[thread overview]
Message-ID: <bug-59021-4-VqCicgdhdw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59021-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-11-06
           Assignee|unassigned at gcc dot gnu.org      |ubizjak at gmail dot com
     Ever confirmed|0                           |1

--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
I have patch in testing.

--cut here--
Index: config/i386/i386.c
===================================================================
--- config/i386/i386.c  (revision 204459)
+++ config/i386/i386.c  (working copy)
@@ -15708,7 +15708,7 @@ ix86_avx_u128_mode_needed (rtx insn)
              rtx arg = XEXP (XEXP (link, 0), 0);

              if (ix86_check_avx256_register (&arg, NULL))
-               return AVX_U128_ANY;
+               return AVX_U128_DIRTY;
            }
        }

--cut here--
>From gcc-bugs-return-433744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 06 17:43:40 2013
Return-Path: <gcc-bugs-return-433744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30532 invoked by alias); 6 Nov 2013 17:43:40 -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 29018 invoked by uid 48); 6 Nov 2013 17:41:38 -0000
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59018] [4.9 Regression] libsanitizer doesn't build for x32
Date: Wed, 06 Nov 2013 17:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kcc at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59018-4-lnXFahagCe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59018-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59018-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: 2013-11/txt/msg00521.txt.bz2
Content-length: 1041

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY018

--- Comment #1 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
At least one of these patches does not build with clang:

/home/kcc/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:807:21:
error: ignored asm label 'r8' on automatic variable [-Werror]
  void *r8 __asm__ ("r8") = newtls;
                    ^
/home/kcc/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:808:21:
error: ignored asm label 'r10' on automatic variable [-Werror]
  int *r10 __asm__ ("r10") = child_tidptr;
                    ^

is this some kind of gcc-specific syntax?
(forgive my ignorance here)

Two general questions:

1. Before doing the merge I test the patch like this:
rm -rf */{*/,}libsanitizer && make -j 50  && make -C gcc check-g{cc,++}
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} asan.exp'

What should I add to this line to also test x32?

2. Is there any chance to test x32 off the clang tree, so that we keep the
upstream tree x32-clean all the time?


  parent reply	other threads:[~2013-11-06 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 11:23 [Bug target/59021] New: " ebotcazou at gcc dot gnu.org
2013-11-06 11:38 ` [Bug target/59021] " rguenth at gcc dot gnu.org
2013-11-06 14:01 ` ubizjak at gmail dot com
2013-11-06 14:38 ` ubizjak at gmail dot com
2013-11-06 17:28 ` ubizjak at gmail dot com [this message]
2013-11-06 17:51 ` ubizjak at gmail dot com
2013-11-06 19:39 ` uros at gcc dot gnu.org
2013-11-14 21:26 ` uros 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-59021-4-VqCicgdhdw@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).