From: Vincent Bernat <bernat@luffy.cx>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: semantic error: not accessible at this address
Date: Mon, 30 Sep 2013 08:12:00 -0000 [thread overview]
Message-ID: <87fvsmd8z4.fsf@guybrush.luffy.cx> (raw)
In-Reply-To: <m3fvsmpz6r.fsf@neo.luffy.cx> (Vincent Bernat's message of "Mon, 30 Sep 2013 09:05:00 +0200")
❦ 30 septembre 2013 09:05 CEST, Vincent Bernat <bernat@luffy.cx> :
>>> I can also advocate to Debian and Ubuntu to use this CFLAGS for future
>>> kernel releases. Is there any drawback to this flag (I assume not)? Is
>>> it still useful when GCC version is fixed? I mean, can we assume that we
>>> will run in future GCC bugs and that will help to workaround them in the
>>> future?
>>
>> I believe it is purely advantageous and worth advocating elsewhere.
>
> I have asked both Ubuntu and Debian to use this flag:
>
> http://bugs.debian.org/724976
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233014
Unfortunately, I discovered that this option was added to GCC 4.7 and
hence is not available in GCC 4.6.3.
--
Make it clear before you make it faster.
- The Elements of Programming Style (Kernighan & Plauger)
prev parent reply other threads:[~2013-09-30 8:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:14 Vincent Bernat
2013-09-27 21:19 ` David Smith
2013-09-27 21:27 ` Vincent Bernat
[not found] ` <y0mvc1mt0k7.fsf@fche.csb>
[not found] ` <8738opg9ym.fsf@guybrush.luffy.cx>
2013-09-27 23:04 ` Frank Ch. Eigler
2013-09-27 23:20 ` Vincent Bernat
2013-09-27 23:25 ` Frank Ch. Eigler
2013-09-27 23:49 ` Vincent Bernat
2013-09-28 0:02 ` Frank Ch. Eigler
2013-09-28 7:48 ` Vincent Bernat
2013-09-28 12:46 ` Frank Ch. Eigler
2013-09-28 16:50 ` [PATCH] PR15123: when PR15123_ASSUME_MFENTRY is set, don't check for -mfentry flag Vincent Bernat
2013-09-28 16:55 ` semantic error: not accessible at this address Vincent Bernat
2013-09-29 14:12 ` Frank Ch. Eigler
2013-09-30 7:05 ` Vincent Bernat
2013-09-30 8:12 ` Vincent Bernat [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=87fvsmd8z4.fsf@guybrush.luffy.cx \
--to=bernat@luffy.cx \
--cc=fche@redhat.com \
--cc=systemtap@sourceware.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).