[gcc] backport of gcc patch to #gcc-7-branch

2017-11-06 Thread Vineet Gupta
Hi, As part of porting glibc to ARC one of the pre-req is to get it to build with upstream toolchain components. The patch 927c0132251f ("[ARC] Configure script to allow non uclibc based triplets") seems to be present in gcc #master, but not in #gcc-7-branch. Can it be backported to gcc 7 plea

Re: [RFC 0/6] glibc port to ARC architecture

2017-11-06 Thread Joseph Myers
On Mon, 6 Nov 2017, Vineet Gupta wrote: > - How do I call it the first time, with my existing version of glibc. > The checkout process, gets upstream glibc and tries to build that instead. build-many-glibcs.py checkout [replace the src/glibc directory there with a different branch if desir

Re: [RFC 0/6] glibc port to ARC architecture

2017-11-06 Thread Vineet Gupta
On 06/27/2017 05:00 AM, Joseph Myers wrote: On Tue, 27 Jun 2017, Florian Weimer wrote: On 06/27/2017 10:00 AM, Vineet Gupta wrote: This is a Request for comments for glibc port to ARC architecture. http://www.synopsys.com/IP/ProcessorIP/ARCProcessors/Pages/default.aspx The Linux kernel, uClib

Re: [RFC 4/6] ARC: Initial port to glibc

2017-11-06 Thread Joseph Myers
On Mon, 6 Nov 2017, Vineet Gupta wrote: > Revisiting glibc upstreaming for ARC. I was told that the lawyers did their > "foo". Do you have the copyright assignment from Synopsys already - or do you > want me to send it to you (privately perhaps) I can confirm the assignment is listed in copyright

Re: [RFC 4/6] ARC: Initial port to glibc

2017-11-06 Thread Vineet Gupta
Hi Joseph, On 06/27/2017 04:56 AM, Joseph Myers wrote: On Tue, 27 Jun 2017, Vineet Gupta wrote: Signed-off-by: Cupertino Miranda Signed-off-by: Vineet Gupta We need ChangeLog entries and copyright assignments, but don't use Signed-off-by. Revisiting glibc upstreaming for ARC. I was told

[PATCH] ARCv2: Accomodate NS48 MMUv5 by releaxing MMU ver checking

2017-11-06 Thread Vineet Gupta
HS48 cpus will have a new MMUv5, although Linux is currently not explicitly supporting the newer features (so remains at V4). The existing software/hardware version check is very tight and causes boot abort. Given that the MMUv5 hardware is backwards compatible, relax the boot check to allow curren