This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Add support for ARM embedded multilibs
- From: "Jasmin J." <jasmin at anw dot at>
- To: Ramana Radhakrishnan <ramana dot radhakrishnan at foss dot arm dot com>, Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, Tejas Belagod <Tejas dot Belagod at arm dot com>
- Date: Wed, 4 Nov 2015 20:31:51 +0100
- Subject: Re: [PATCH] Add support for ARM embedded multilibs
- Authentication-results: sourceware.org; auth=none
- References: <56395178 dot 8000006 at anw dot at> <CAJA7tRbQPN2HDtP3HjASn6W5s=Lg83k9+DDDJ92_GjDAs95BBw at mail dot gmail dot com> <5639C54F dot 5070700 at anw dot at> <5639D355 dot 7080900 at foss dot arm dot com>
Hello Ramana!
> There are usually features on the embedded-X_X-branch used to create
> releases that may not be on an FSF release branch.
Not on the embedded-5 branch and as far as I analysed it, all changes of
embedded-4.9 branch are now at Trunk.
>> I would like to ask if you have a copyright assignment on file with the
>> FSF
> So, you don't have one ? In which case it may make more sense for Tejas to
> deal with this given he can handle it under ARM's copyright assignment. If
> you make changes to this without a copyright assignment on file and submit
> it, it may be difficult to review this from a copyright position.
So shall I communicate with Tejas instead of gcc-patches?
On the other hand I just read
" Small changes can be accepted without a copyright disclaimer or a copyright
assignment on file. "
And at the end, it is the same code as Terry's patch. But I will investigate
the things you mentioned in your first answer, if they are really required and
if no simplify the patch.
> Changing the way in which you build GCC is a real change to GCC that affects
> many developers.
Does it really? It is enabled only, if you use the "--with-multilib-list"
configure option. Without the option, gcc is build exactly the same.
Without the patch "--with-multilib-list" even to allowed for any ARM target.
> I think mapping all the remaining -mcpu=cortex-a* cores and -mcpu=cortex-m*
> cores in there would be a sensible first step.
THX for the hint.
BR
Jasmin