GNU Arm Embedded Toolchain

4.9 2015q1 BigEndian patch

Asked by jdobry

Big endian multilib support for 4.9. 2015q1 is here

http://pastebin.com/aKTCXtab

Works fine, enjoy :-)

Question information

Language:
English Edit question
Status:
Solved
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Solved by:
jdobry
Solved:
Last query:
Last reply:
Revision history for this message
Joey Ye (jinyun-ye) said : 		#1

Jiri,

If you can sign FSF assignment, this patch then can be included into product releases.

Thanks,
Joey

Revision history for this message
jdobry (jdobry) said : 		#2

I thing that I don't need to sign FSF assigment.
Quotation from https://www.gnu.org/prep/maintain/maintain.html#Legal-Matters
"A change of just a few lines (less than 15 or so) is not legally significant for copyright."

And this patch change only 11 lines :-) And yes it is fully under GPL license.

If you insist to have signed paper for FSF it is not problem.
Is it this form? http://web.cvs.savannah.gnu.org/viewvc/gnulib/Copyright/request-assign.changes?revision=1.2&root=gnulib&view=markup

Revision history for this message
Joey Ye (jinyun-ye) said : 		#3

Yes

Revision history for this message
jdobry (jdobry) said : 		#4

This patch can be used with 2015q3 without changes.

It is here http://pastebin.com/aKTCXtab

PS: We are using BE multilib patch over 3 years. When it will be used on default package?

Revision history for this message
Tejas Belagod (belagod-tejas) said : 		#5

Hi,

This patch will have to submitted upstream on the gcc-patches mailing list before we can pull this into GNU embedded tools releases to make it default.

I can't see any progress on this patch having been submitted upstream on public GCC mailing lists. Do you have more info?

Thanks,
Tejas.

Revision history for this message
Thomas Garcia (toemossgarcia) said : 		#6

@jdobry Thanks for sharing! I used your changes in a patch I made that also changes the toolchain prefix from arm-none to armeb-none::

https://gist.github.com/tgarc/3094325d61797d3ee0e3

I'm also curious about what the status of this patch is. Any updates on this???

Cheers,

Thomas

Revision history for this message
jdobry (jdobry) said : 		#7

@Thomas Garcia :

But sorry I don't have any news about integration into this project. It wait over 3 years. For this problem also exist patch from google guys (with FSF agreement) but we are still waiting.
By my informations problem is small motivation of package maintainers to build test platform. They are not want to release this functionality without tests, obviously.

Jiri