That breaks Ada:
a-teioed.adb: In function 'Ada.Text_Io.Editing.Format_Number':
a-teioed.adb:127:4: error: alignment of array elements is greater than element
size
a-teioed.adb:127:4: error: alignment of array elements is greater than element
size
a-teioed.adb:127:4: error: alignment of array el
> Things we may want to remove:
>
> - references to java in contrib (download_ecj, gcc_update,
> patch_tester.sh, update-copyright.py)
> - GCJ, GCJ_FOR_BUILD, GCJ_FOR_TARGET in Makefiles.tpl and configure.ac
> - LIBGCJ_SONAME in config/i386/{cygwin.h,mingw32.h}
> - references to java in install.
On Sat, Oct 29, 2016 at 09:07:42AM +, Bernd Edlinger wrote:
> > Things we may want to remove:
> >
> > - references to java in contrib (download_ecj, gcc_update,
> > patch_tester.sh, update-copyright.py)
> > - GCJ, GCJ_FOR_BUILD, GCJ_FOR_TARGET in Makefiles.tpl and configure.ac
> > - LIBGCJ_S
On 28/10/16 15:39 -0400, Tim Song wrote:
On Fri, Oct 28, 2016 at 1:47 PM, Jonathan Wakely wrote:
For some reason the Filesystem library says that you can construct
paths from iterators with value_type that is a possibly const encoded
character type. I don't know why we support const value_type
On Fri, Oct 28, 2016 at 09:42:10PM -0600, Jeff Law wrote:
>
> Consider this definition of ASM_GENERATE_INTERNAL_LABEL (from sp64-elf.h):
>
> #undef ASM_GENERATE_INTERNAL_LABEL
> #define ASM_GENERATE_INTERNAL_LABEL(LABEL,PREFIX,NUM) \
> sprintf ((LABEL), "*.L%s%ld", (PREFIX), (long)(NUM))
>
Hi,
> Sadly, there's a bigger issue here. Namely that the caller and the
> definition of ASM_GENERATE_INTERNAL_LABEL both can include arbitrary
> length text into the label name. Furthermore, the buffer is allocated
> in the caller's context. It's a terrible API.
Yes. Even ASM_FORMAT_PRIVAT
On Sat, Oct 29, 2016 at 10:07:22AM +0200, Andreas Schwab wrote:
> That breaks Ada:
>
> a-teioed.adb: In function 'Ada.Text_Io.Editing.Format_Number':
> a-teioed.adb:127:4: error: alignment of array elements is greater than
> element size
> a-teioed.adb:127:4: error: alignment of array elements is
Hi!
As the testcases show, we mishandle e.g. -std=c++11 -std=gnu++14
or -std=c++11 -std=c++98, in that earlier -std=c++{1[147yz],0x}
disables -fext-numeric-literals and nothing turns this again on,
unless enabled explicitly, eventhough such option combinations
should just ignore the earlier -std=
On Fri, Oct 28, 2016 at 10:59:35AM +0200, Jakub Jelinek wrote:
> On Fri, Oct 28, 2016 at 10:52:34AM +0200, Richard Biener wrote:
> > > I've already committed the original patch based on Eric's review, but
> > > managed to come up with another testcase that still ICEs (one with two
> > > different c
The attached patch changes the malloc ABI alignment to 128 bits on hppa64 and
hppa-linux.
This suppresses the over-aligned new warning seen on linux. On hppa64, we now
match the
alignment for long double.
The default definition of MALLOC_ABI_ALIGNMENT is 32. This is wrong for
PA-RISC, so I ba
On a small number of ports, we only have 2 defined register classes.
NO_REGS and ALL_REGS. Examples would include nvptx and vax.
So let's look at check_and_process_move from lra-constraints.c:
sclass = dclass = NO_REGS;
if (REG_P (dreg))
dclass = get_reg_class (REGNO (dreg));
if (d
On Sat, Oct 29, 2016 at 12:09 PM, Jakub Jelinek wrote:
> Apparently the driver reorders the options, -std=* options come before
> all -f* options, so both of the following patches work the same, except
> when cc1plus is invoked by hand. The first (inlined) patch solves it
> more in line how e.g.
The attached patch changes the define of FINI_SECTION_ASM_OP to match that of
INIT_SECTION_ASM_OP.
Tested on hppa64-hp-hpux11.11. Committed to trunk.
Dave
--
John David Anglin dave.ang...@bell.net
2016-10-29 John David Anglin
* config/pa/pa64-hpux.h (FINI_SECTION_ASM_OP): De
On Sat, Oct 29, 2016 at 12:41:43PM -0400, Jason Merrill wrote:
> On Sat, Oct 29, 2016 at 12:09 PM, Jakub Jelinek wrote:
> > Apparently the driver reorders the options, -std=* options come before
> > all -f* options, so both of the following patches work the same, except
> > when cc1plus is invoked
Hi Kyrill!
On Mon, 2016-10-24 15:56:48 +0100, Kyrill Tkachov
wrote:
> This is a slight update over [1] with Richard's feedback addressed.
> In terminate_all_aliasing_chains we now terminate the chain early if
> the destination is writing to a base offset by a variable amount.
> This avoids walki
On Fri, Oct 28, 2016 at 09:12:29AM -0600, Jeff Law wrote:
>
> The PPC port is stumbling over the new integer in boolean context warnings.
>
> In particular this code from rs6000_option_override_internal is
> problematical:
>
> HOST_WIDE_INT flags = ((TARGET_DEFAULT) ? TARGET_DEFAULT
>
On 2016.10.29 at 19:56 +0200, Jan-Benedict Glaw wrote:
> Hi Kyrill!
>
> On Mon, 2016-10-24 15:56:48 +0100, Kyrill Tkachov
> wrote:
> > This is a slight update over [1] with Richard's feedback addressed.
> > In terminate_all_aliasing_chains we now terminate the chain early if
> > the destination
On October 29, 2016 6:12:50 PM GMT+02:00, Jakub Jelinek
wrote:
>On Fri, Oct 28, 2016 at 10:59:35AM +0200, Jakub Jelinek wrote:
>> On Fri, Oct 28, 2016 at 10:52:34AM +0200, Richard Biener wrote:
>> > > I've already committed the original patch based on Eric's review,
>but
>> > > managed to come up
On October 29, 2016 5:57:17 PM GMT+02:00, Jakub Jelinek
wrote:
>On Sat, Oct 29, 2016 at 10:07:22AM +0200, Andreas Schwab wrote:
>> That breaks Ada:
>>
>> a-teioed.adb: In function 'Ada.Text_Io.Editing.Format_Number':
>> a-teioed.adb:127:4: error: alignment of array elements is greater
>than elem
Hi All,
Gfortran currently treats an L format descriptor with no width as an extension.
When the width is zero (not a positive integer) the error message was confused.
The checking software was saving the format token, FMT_ZERO, for the next round
of checks and this was interpreted to be a zer
20 matches
Mail list logo
