> -Original Message-
> From: Terry Guo
> Sent: Tuesday, November 11, 2014 9:08 AM
> To: Richard Earnshaw; Joel Sherrill
> Cc: GCC Mailing List
> Subject: RE: arm/thumb broken on head
>
>
>
> > -Original Message-
> > From: Richard Earnshaw
> -Original Message-
> From: Richard Earnshaw
> Sent: Tuesday, November 11, 2014 1:08 AM
> To: Joel Sherrill; GCC Mailing List
> Cc: Terry Guo
> Subject: Re: arm/thumb broken on head
>
> On 10/11/14 15:26, Joel Sherrill wrote:
> > Hi
> >
> >
Hi There,
To facilitate the development for ARM embedded processors, I just created
the GCC embedded-4_9-branch.
The branch is described at http://gcc.gnu.org/svn.html.
The branch can be viewed at
http://gcc.gnu.org/viewcvs/gcc/branches/ARM/embedded-4_9-branch/.
You are welcome to submit patch
> -Original Message-
> From: Ilya Enkovich [mailto:enkovich@gmail.com]
> Sent: Monday, August 12, 2013 4:37 PM
> To: Terry Guo
> Cc: GCC Development
> Subject: Re: How to specify multiple OSDIRNAME suffixes for multilib
> (Multilib usage with MPX)?
>
>
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> Ilya Enkovich
> Sent: Friday, August 09, 2013 8:37 PM
> To: GCC Development
> Subject: How to specify multiple OSDIRNAME suffixes for multilib (Multilib
> usage with MPX)?
>
> Hi,
>
> I'm cu
On Wed, May 8, 2013 at 6:14 PM, gnubie gnubie wrote:
> Hi,
> I've noticed odd behaviour when building an ARM compiler with GCC 4.7,
> --with-mode=thumb and multilibs enabled.
>
> If I do a standard c/c++ newlib build with the following multilib options:
> MULTILIB_OPTIONS += marm mthumb
> MULT
Hi,
I have following code which will be built with options
"-ffunction-sections -fdata-sections -Wl,--gc-sections
-Wl,-Map=test.map":
#include
static int unusedint=5;
static int usedint=1;
int unused(void) {
return 1;
}
int foo(void) {
return usedint;
}
int main(void) {
if (fo
>
> "Terry Guo" writes:
>
> > make[1]: *** [check-recursive] Error 1
> > make[1]: Target `check' not remade because of errors.
> > make[1]: Leaving directory
> > `/home/build/gcc-4-7-daily-test/build-linux/gcc-final/arm-none-
> eabi/libstdc+
Hi,
I plan to set up daily regression test on trunk for target
ARM-NONE-EABI and post results to gcc-testresults mailing list. Which
Binutils should I use, the Binutils trunk or the latest released
Binutils? And which way is recommended, building from a combined tree
or building separately? If the
Hello,
I configured my gcc with "--disable-tls" for arm-none-eabi. But it can
still successfully compile the below case:
__thread int i;
int f (void) { return i; }
void main (int j) { i = j; }
The "dg-require-effective-target tls" use this case to check whether
target supports
10 matches
Mail list logo
