public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Seurer <seurer@linux.vnet.ibm.com>
To: Andrew Pinski <pinskia@gmail.com>, Jerry DeLisle <jvdelisle@charter.net>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
	       Janne Blomqvist <blomqvist.janne@gmail.com>,
	       "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, libfortran] AMD-specific versions of library matmul
Date: Fri, 26 May 2017 15:33:00 -0000	[thread overview]
Message-ID: <33b0bb09-4b5d-e81a-f86a-e3078ce88af4@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+=Sn1mFUm_88s3y6AuKgvwFR3t5C6RML-=uJLGyRDc4710Bng@mail.gmail.com>

On 05/26/2017 12:41 AM, Andrew Pinski wrote:
> On Thu, May 25, 2017 at 6:43 PM, Jerry DeLisle <jvdelisle@charter.net> wrote:
>> On 05/25/2017 02:57 PM, Thomas Koenig wrote:
>>>
>>> Hi everybody,
>>>
>>> I have committed the patch (with the corrections for the name)
>>> as rev 248472.
>>>
>>> The infrastructure is in place, so we will be able to make
>>> any fine-tuning easily.
>>>
>>> Regards
>>>
>>>      Thomas
>>
>>
>> Based on my testing I think it is close enough as is.
>
> This patch most likely broke all non-x86 targets:
> configure: error: conditional "HAVE_AVX128" was never defined.
> Usually this means the macro was only invoked conditionally.
> Makefile:19843: recipe for target 'configure-target-libgfortran' failed
> make[1]: *** [configure-target-libgfortran] Error 1
> make[1]: *** Waiting for unfinished jobs....

Yup, this is definitely what broke (most-) everything.  248471 worked 
fine and then the above error starting with 248472.
-- 

-Bill Seurer

      reply	other threads:[~2017-05-26 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <96c89d30-d311-22e6-e80d-8b87c68d3c60@netcologne.de>
2017-05-25 11:19 ` Fwd: " Thomas Koenig
2017-05-25 14:11 ` Jerry DeLisle
2017-05-25 14:52   ` Thomas Koenig
2017-05-25 17:58 ` Janne Blomqvist
2017-05-25 20:31   ` Jerry DeLisle
2017-05-25 23:44     ` Thomas Koenig
2017-05-26  5:41       ` Jerry DeLisle
2017-05-26  6:21         ` Andrew Pinski
2017-05-26 15:33           ` Bill Seurer [this message]

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=33b0bb09-4b5d-e81a-f86a-e3078ce88af4@linux.vnet.ibm.com \
    --to=seurer@linux.vnet.ibm.com \
    --cc=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    --cc=pinskia@gmail.com \
    --cc=tkoenig@netcologne.de \
    /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).