> Jakub Jelinek <ja...@redhat.com> writes:
>
> > On Thu, Oct 23, 2014 at 11:35:44AM +0200, Rainer Orth wrote:
> >> > The testcase is clearly i?86/x86_64 specific, so it must be guarded with
> >> > { target i?86-*-* x86_64-*-* }, and as it is a compile time test, no need
> >>
> >> Right, that's what my patch already does.
> >>
> >> > for assembler support, so just adding -msse2 option to dg-option is the
> >> > right thing to do.
> >>
> >> Ok, will try that. Still no idea why Linux/x86 and Solaris/x86 are
> >> different here.
> >
> > Why do you think so? I certainly have:
> > FAIL: gcc.dg/ipa/ipa-icf-21.c (test for excess errors)
> > UNRESOLVED: gcc.dg/ipa/ipa-icf-21.c scan-ipa-dump icf "Equal symbols: 1"
> > UNRESOLVED: gcc.dg/ipa/ipa-icf-21.c scan-ipa-dump icf "Semantic equality
> > hit:bar->foo"
> > in my i686-linux test_summary log. It really depends on how the compiler
>
> Right, but on i386-pc-solaris2.11 it passes.
>
> > is configured, if it defaults to march that has sse/sse2 by default, it will
> > succeed, otherwise it will not.
>
> I had a terrible time figuring out what march value
> i686-unknown-linux-gnu uses; only in gcc -v it's possible to see that it
> uses pentiumpro, unlike pentium4 on Solaris/x86, which explains the
> difference.
What is the reason to use pentium4 for Solaris/x86? Is it -march setting or
-mtune? For -mtune it is a terrible choice....
Honza
>
> Thanks.
> Rainer
>
> --
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
