On 2 February 2015 at 21:11, Jonny Grant wrote:
> Is this a consensus agreement to rename those .C -> .cc ?
No.
On 2 February 2015 at 21:54, Paul Shortis wrote:
> I could have avoided the expander and used a single instruction pattern for
> a)b)c) if if could have found a way to have alternative dependent clobbers
> in an instruction pattern. I investigated attributes but couldn't see how I
> would be able
On 02/02/15 18:55, Yury Gribov wrote:
On 01/30/2015 11:16 AM, Matthew Fortune wrote:
Yury Gribov writes:
On 01/29/2015 08:32 PM, Richard Henderson wrote:
On 01/29/2015 02:08 AM, Paul Shortis wrote:
I've ported GCC to a small 16 bit CPU that has single bit
shifts. So
I've handled variable / m
On Mon, Feb 2, 2015 at 1:11 PM, Jonny Grant wrote:
>
>
> On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
>>
>>
>>> Am 01.02.2015 um 17:09 schrieb Eli Zaretskii :
>>>
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely
Cc: Andrew Pinski , "gcc@gcc.gnu.org"
,
On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii :
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely
Cc: Andrew Pinski , "gcc@gcc.gnu.org" , Jonny
Grant
These files are only compiled by GCC's own build system, with GCC's
o
On Fri, 2015-01-30 at 23:24 +0100, Kevin Ingwersen (Ingwie Phoenix)
wrote:
> > Am 30.01.2015 um 22:39 schrieb DJ Delorie :
> >
> >
> > pins...@gmail.com writes:
> >> No because they are c++ code so capital C is correct.
> >
> > However, we should avoid relying on case-sensitive file systems
> >
Hi,
On Mon, 2 Feb 2015, Tom de Vries wrote:
> I've minimized the vaarg-4a.c failure, and added it as testcase to the patch
> series as gcc.target/x86_64/abi/callabi/vaarg-4.c.
>
> The problem is in this code:
> ...
> e = va_arg (argp, char *);
> e = va_arg (argp, char *);
> ...
>
> which is
On 30-01-15 14:11, Michael Matz wrote:
Hi,
On Fri, 30 Jan 2015, Tom de Vries wrote:
Maybe you want to pick up the work?
In principle yes, depending on the amount of work (at this point I have no
idea what remains to be done and how long that would take me).
Michael, are your patches posted
On 01/30/2015 11:16 AM, Matthew Fortune wrote:
Yury Gribov writes:
On 01/29/2015 08:32 PM, Richard Henderson wrote:
On 01/29/2015 02:08 AM, Paul Shortis wrote:
I've ported GCC to a small 16 bit CPU that has single bit shifts. So
I've handled variable / multi-bit shifts using a mix of inline s
On Sat, Jan 31, 2015 at 05:09:29PM -0700, Simon Glass wrote:
> I have been fighting with a strange problem on ARM where gcc puts all
> the .rodata from a number of files lumped into a single .rodata
> section even when -fdata-sections is used.
>
> I searched and found a bug report here:
>
> https
Dear gcc developer,
I have a code like this:
#include
void foo(int x)
{
int y;
x++;
y = 4;
}
int main(void)
{
foo(2);
return 0;
}
and compiled with "gcc -o outexec srcfile.c" command.
when disassemble the file we see that sending argument to function
"foo" is done by
11 matches
Mail list logo
