On Mon, May 30, 2016 at 5:15 PM, Prasad Ghangal
wrote:
> Hi,
>
> As David suggested in his rtlfe patch,
> this patch recognizes __GIMPLE keyword and switches to
> c_parser_parse_gimple_body by providing -fgimple option.
>
>
> diff --git a/gcc/c-family/c-common.c b/gcc/c-family/c-common.c
> index 4
Hi Richard,
On 27/05/16 12:43, Richard Biener wrote:
The first release candidate for GCC 5.4 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/5.4.0-RC-20160527
and shortly its mirrors. It has been generated from SVN revision 236809.
I have sofar bootstrapped the release candidate on x
On Tue, 31 May 2016, Kyrill Tkachov wrote:
> Hi Richard,
>
> On 27/05/16 12:43, Richard Biener wrote:
> > The first release candidate for GCC 5.4 is available from
> >
> > ftp://gcc.gnu.org/pub/gcc/snapshots/5.4.0-RC-20160527
> >
> > and shortly its mirrors. It has been generated from SVN re
On 31/05/16 12:17, Richard Biener wrote:
On Tue, 31 May 2016, Kyrill Tkachov wrote:
Hi Richard,
On 27/05/16 12:43, Richard Biener wrote:
The first release candidate for GCC 5.4 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/5.4.0-RC-20160527
and shortly its mirrors. It has been
Richard, Jakub, or any global write maintainer: can I get a review on this
one-word patch?
--
The attached patch allows libgomp to install its Fortran modules in the correct
multilib-aware directories, just like libgfortran does.
Without it, multilib Fortran OpenMP code using th
On Tue, May 31, 2016 at 03:36:14PM +0200, FX wrote:
> Richard, Jakub, or any global write maintainer: can I get a review on this
> one-word patch?
>
> --
>
> The attached patch allows libgomp to install its Fortran modules in the
> correct multilib-aware directories, just like l
Hi,
avr-gcc was crashing for below test case.
command line: avr-gcc -mmcu=atmega328p -O1 test.c
struct ResponseStruct{
unsigned char responseLength;
char *response;
};
static char response[5];
struct ResponseStruct something(){
struct ResponseStruct returnValue;
returnValue.responseLengt
On Mon, May 30, 2016 at 3:15 PM, Patrick Palka wrote:
> Though there are some inconsistencies regarding the inclusiveness of
> -Wall seeing as neither -Woverlength-strings nor -Wempty-body are
> enabled by -Wall even though they seemingly satisfy the criteria of
> -Wall more readily than -Wmislead
> Why? It should look for it first in 32/finclude, sure, but if not found,
> should fall back to finclude dir, where it is found.
> Does it differ between 32-bit and 64-bit compilation?
Module files are target- and ABI-dependent and can differ between multilibs.
Thus gfortran only looks for intr
On 05/29/2016 12:59 AM, Woon yung Liu wrote:
Hi Richard,
I have solved the problems with the mulv8hi3 pattern; I needed to adjust the
code within mips.c to allow the double-sized vector modes and to allow vector
modes into the LO+HI accumulators.
Yes, I should have mentioned that you would n
10 matches
Mail list logo
