From: Kyle McMartin <kyle@infradead.org>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, jstancek@redhat.com,
keescook@chromium.org, peter.oberparleiter@de.ibm.com,
linux-arch@vger.kernel.org, arnd@arndb.de, mgahagan@redhat.com,
agospoda@redhat.com, akpm@linux-foundation.org
Subject: Re: [PATCH v2 4/4] kernel: add support for init_array constructors
Date: Fri, 6 Sep 2013 14:07:51 -0400 [thread overview]
Message-ID: <20130906180751.GD25882@merlin.infradead.org> (raw)
In-Reply-To: <20130906175118.GB2332@localhost.localdomain>
On Fri, Sep 06, 2013 at 07:51:18PM +0200, Frantisek Hrbata wrote:
> > > v2: - reuse mod->ctors for .init_array section for modules, because gcc uses
> > > .ctors or .init_array, but not both at the same time
> > >
> > > Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
> >
> > Might be nice to document which gcc version changed this, so people can
> > choose whether to cherry-pick this change?
>
> Thank you for pointing this out. As per gcc git this was introduced by commit
> ef1da80 and released in 4.7 version.
>
> $ git describe --contains ef1da80
> gcc-4_7_0-release~4358
>
> Do you want me to post v3 with this info included in the descrition?
>
It actually depends on the combination of binutils/ld and gcc you use, not
simply which gcc version you use. :/
--Kyle
next prev parent reply other threads:[~2013-09-06 18:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 14:42 [PATCH v2 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 1/4] gcov: move gcov structs definitions to a gcc version specific file Frantisek Hrbata
2013-09-04 14:42 ` Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 2/4] gcov: add support for gcc 4.7 gcov format Frantisek Hrbata
2013-09-04 14:42 ` Frantisek Hrbata
2013-09-18 21:22 ` Andrew Morton
2013-09-18 21:27 ` Joe Perches
2013-09-18 21:27 ` Joe Perches
2013-09-18 21:31 ` Andrew Morton
2013-09-19 10:12 ` Frantisek Hrbata
2013-09-19 9:04 ` Peter Oberparleiter
2013-09-19 10:21 ` Frantisek Hrbata
2013-09-19 10:31 ` Peter Oberparleiter
2013-09-04 14:42 ` [PATCH v2 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-09-04 14:42 ` Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 4/4] kernel: add support for init_array constructors Frantisek Hrbata
2013-09-04 14:42 ` Frantisek Hrbata
2013-09-06 2:13 ` Rusty Russell
2013-09-06 17:51 ` Frantisek Hrbata
2013-09-06 18:07 ` Kyle McMartin [this message]
2013-09-09 1:14 ` Rusty Russell
2013-09-09 1:14 ` Rusty Russell
2013-09-09 16:28 ` Frantisek Hrbata
2013-09-10 0:15 ` Kyle McMartin
2013-09-10 5:35 ` Rusty Russell
2013-09-10 13:28 ` Frantisek Hrbata
2013-09-10 13:28 ` Frantisek Hrbata
2013-09-11 1:52 ` Rusty Russell
2013-09-26 23:11 ` [PATCH v2 0/4] add support for gcov format introduced in gcc 4.7 Christophe Guillon
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=20130906180751.GD25882@merlin.infradead.org \
--to=kyle@infradead.org \
--cc=agospoda@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=fhrbata@redhat.com \
--cc=jstancek@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgahagan@redhat.com \
--cc=peter.oberparleiter@de.ibm.com \
--cc=rusty@rustcorp.com.au \
/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 NNTP newsgroup(s).