From: Josh Stone <jistone@redhat.com>
To: Michal Marek <mmarek@suse.cz>, linux-kernel@vger.kernel.org
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
"Jakub Jelinek" <jakub@redhat.com>,
"Josh Boyer" <jwboyer@fedoraproject.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Markus Trippelsdorf" <markus@trippelsdorf.de>,
"Michel Dänzer" <michel@daenzer.net>
Subject: Re: [PATCH RESEND] Kbuild: Add an option to enable GCC VTA
Date: Mon, 24 Nov 2014 15:46:42 -0800 [thread overview]
Message-ID: <5473C362.80308@redhat.com> (raw)
In-Reply-To: <5473A74F.8000709@suse.cz>
On 11/24/2014 01:46 PM, Michal Marek wrote:
> Dne 21.11.2014 v 19:40 Josh Stone napsal(a):
>> Due to recent codegen issues, gcc -fvar-tracking-assignments was
>> unconditionally disabled in commit 2062afb4f804a ("Fix gcc-4.9.0
>> miscompilation of load_balance() in scheduler"). However, this reduces
> [...]
>> With gcc-4.9.2-1.fc22, I can now build v3.18-rc5 with Fedora's i686 and
>> x86_64 configs, and this is completely clean with GCC_COMPARE_DEBUG.
>
> According to gcc's bug#61801, this is really fixed in 4.9.2 (commit
> 556537c4 in the git mirror). So how about checking for this minimal
> version instead of a new Kconfig option?
That's possible, if the new Kconfig option is really undesirable. But
given that there's a similar DWARF4 option, which this pairs well with,
I thought a VTA option was a good choice.
Besides 4.9.2 though, this particular fix has also been backported to
4.8.4, and who knows what various distro maintainers may do.
next prev parent reply other threads:[~2014-11-24 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:40 [PATCH RESEND] Kbuild: Add an option to enable GCC VTA Josh Stone
2014-11-24 21:46 ` Michal Marek
2014-11-24 23:46 ` Josh Stone [this message]
2014-11-25 21:05 ` Michal Marek
2014-11-25 21:24 ` Josh Boyer
2015-04-23 21:25 ` [PATCH] " Frank Ch. Eigler
2015-04-24 12:40 ` Josh Boyer
2015-04-24 13:42 ` Frank Ch. Eigler
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=5473C362.80308@redhat.com \
--to=jistone@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fche@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jakub@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=michel@daenzer.net \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.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 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.