All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Turner <dturner@twopensource.com>
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: 745224e0 gcc-4.9 emmintrin.h build error
Date: Thu, 10 Jul 2014 15:58:24 -0700	[thread overview]
Message-ID: <1405033104.3775.10.camel@stross> (raw)
In-Reply-To: <CAOvwQ4in4aufZX2PGkAoX4vWhg_mq+n6Baov_ifGjiyfR_UbPQ@mail.gmail.com>

On Fri, 2014-07-11 at 00:12 +0200, Tuncer Ayaz wrote:
> Sorry, didn't test properly when I tried with/without config.mak, and
> PROFILE=BUILD was the problem. I had that in config.mak based on
> information gathered from INSTALL and Makefile. To be clear, is
> PROFILE=BUILD (still) supported?

For what it's worth, the problem seems to depend on the combination of
-DNO_NOTRETURN=1 and -fprofile-use.  So I can trigger the same breakage
with this:
---
#define NO_NORETURN 1
#include "git-compat-util.h"

int main() {}
---
gcc -I. -c -fprofile-use=/tmp foo.c -o foo.o

Do we still need NO_NORETURN?  Git seems to build without it under GCC
4.6.3 (Ubuntu's version).  

  reply	other threads:[~2014-07-10 22:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 19:59 745224e0 gcc-4.9 emmintrin.h build error Tuncer Ayaz
2014-07-10 20:06 ` Tuncer Ayaz
2014-07-10 20:23 ` Jeff King
2014-07-10 20:43   ` Tuncer Ayaz
2014-07-10 20:33 ` David Turner
2014-07-10 20:44   ` Tuncer Ayaz
2014-07-10 20:53     ` David Turner
2014-07-10 21:59       ` Tuncer Ayaz
2014-07-10 22:12         ` Tuncer Ayaz
2014-07-10 22:58           ` David Turner [this message]
2014-07-12  4:56           ` Jeff King
2014-07-12  8:47             ` Tuncer Ayaz
2014-07-14  6:00               ` Jeff King
2014-07-12  8:53             ` Tuncer Ayaz
2014-07-14  6:04               ` Jeff King

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=1405033104.3775.10.camel@stross \
    --to=dturner@twopensource.com \
    --cc=git@vger.kernel.org \
    --cc=tuncer.ayaz@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.