public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tema at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50704] FAIL: gcc.target/i386/warn-vect-op-1.c
Date: Wed, 12 Oct 2011 17:04:00 -0000	[thread overview]
Message-ID: <bug-50704-4-U27DfUduAB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50704-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Artem Shinkarov <tema at gcc dot gnu.org> 2011-10-12 17:03:46 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Ah! It happens because the underlying architecture is 32-bit.  We should run
> > > these tests only on 64-bit architectures to get the correct warnings.  So I'll
> > > add /* { dg-require-effective-target lp64 } */ option.
> > >
> > > By the way, is it a correct option to disable running the test on 32-bit archs?
> > > 
> > > 
> > 
> > X86 supports ia32, x32 and lp64.  I think you want to run it for x32 and
> > lp32.
> 
> I meant "x32 and lp64".

So if I want to run the test only on 64-bit architectures, then lp64 is the
correct choice in dg-require-effective-target?

Artem.


  parent reply	other threads:[~2011-10-12 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 15:39 [Bug middle-end/50704] New: " hjl.tools at gmail dot com
2011-10-12 15:45 ` [Bug middle-end/50704] " dominiq at lps dot ens.fr
2011-10-12 16:57 ` tema at gcc dot gnu.org
2011-10-12 17:02 ` hjl.tools at gmail dot com
2011-10-12 17:03 ` hjl.tools at gmail dot com
2011-10-12 17:04 ` tema at gcc dot gnu.org [this message]
2011-10-12 17:36 ` hjl.tools at gmail dot com
2011-10-12 17:45 ` tema at gcc dot gnu.org
2011-10-12 17:58 ` hjl.tools at gmail dot com
2011-10-14 15:40 ` tema at gcc dot gnu.org
2021-09-02  9:06 ` [Bug testsuite/50704] " pinskia at gcc dot gnu.org
2021-09-02  9:06 ` pinskia 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-50704-4-U27DfUduAB@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).