On 03/10/2017 10:51 PM, Jeff Law wrote:
On 03/10/2017 09:20 AM, Martin Sebor wrote:
On 03/10/2017 05:57 AM, Rainer Orth wrote:
Hi Segher,
On Fri, Feb 10, 2017 at 11:56:39AM +0100, Rainer Orth wrote:
Segher Boessenkool writes:
As stated in the PR, this test now passes on aarch64, ia64, pow
r243470 decorates standard allocation functions like alloca
and malloc with attribute alloc_size. However, in applying
the attribute to aligned_alloc I had overlooked that the size
argument is the second one and not the first. That oversight
has led to __builtin_object_size() reporting the wrong
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
http://translationproject.org/latest/gcc/de.po
(This file, 'gcc-7.1-b20170226.de.po', h
On 03/12/2017 02:07 PM, Gerald Pfeifer wrote:
> On Thu, 9 Mar 2017, Thomas Preudhomme wrote:
>> JonY: what about the attached patch to document the change of behavior
>> of GCC on Windows depending on the configure option used?
>
> +MinGW issues
> +
> +GCC on Microsoft Windows can now be configure
Hi Martin,
On Mon, 27 Feb 2017, Martin Sebor wrote:
> Sorry to be jumping in so late. I only noticed this bit now.
>
> I would suggest to say that these new built-ins evaluate to integer
> constant expressions when their arguments do. Not all C programmers
> are familiar with C++ constexpr so th
On Wed, 24 Aug 2016, Richard Biener wrote:
> We've been creating those lazily over the last decade. We can change
> that, an entry for releasing.html is appreciated then so we don't forget.
And here we go, in time for the release of GCC 7 / branching of GCC 8.
(Except, this time I went ahead an
While integrating the d_printing recursion guard change into gdb I
noticed we forgot to initialize the demangle_component d_printing
field in cplus_demangle_fill_{name,extended_operator,ctor,dtor}.
As is done in cplus_demangle_fill_{component,builtin_type,operator}.
It happened to work because in g
From: Gerald Pfeifer
Date: Sun, 12 Mar 2017 12:39:56 +0100 (CET)
> On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
>> References to dependencies on really, really old versions of
>> binutils (talking 10+ years here) which I think we can remove.
>> Let me follow-up with some of you with concrete sugges
On Fri, 10 Mar 2017, Manuel López-Ibáñez wrote:
>> I am currently translating GCC into German. During that, I noticed that
>> in some places the term "zero character" means '\0'. The official term
>> though is "null character", as per the C standard.
> I don't see anything explicit here: https://gc
Hello world,
the attached patch fixes another occurence of PR 79956.
In this case, we did
sdim = GFC_DESCRIPTOR_RANK (source);
..
for (n = 0; n < sdim; n++)
{
sstride[n] = GFC_DESCRIPTOR_STRIDE(source,n)
}
Now, we know that sdim can never be zero or lower,
On Sun, Mar 12, 2017 at 7:26 PM, NightStrike wrote:
> On Mon, Feb 27, 2017 at 6:15 AM, Janne Blomqvist
> wrote:
>> Don't try to use rand_s on CYGWIN
>>
>> CYGWIN seems to include _mingw.h and thus __MINGW64_VERSION_MAJOR is
>> defined even though rand_s is not available. Thus add an extra check
>
> Date: Sun, 12 Mar 2017 14:47:42 +0100
> From: Gerald Pfeifer
> (May there be further changes to consider for cris-*?)
Nothing actively pursued and no news on related issues.
brgds, H-P
now on this.
Testsuite run completed with no change in results:
=== gfortran Summary ===
# of expected passes44633
# of unexpected failures55
# of unexpected successes 6
# of expected failures 85
# of unsupported tests 187
/tmp/build/gcc
On 03/12/2017 12:29 PM, Nicolas Koenig wrote:
Hello everyone,
this is my first attempt at a patch. The necessary paperwork for me to
contribute is all said & done. I'm looking forward to some more compiler
hacking :)
Nicolas
Here is the changelog:
2017-03-12 Nicolas Koenig
Hello everyone,
this is my first attempt at a patch. The necessary paperwork for me to
contribute is all said & done. I'm looking forward to some more compiler
hacking :)
Nicolas
Here is the changelog:
2017-03-12 Nicolas Koenig
PR fortran/39239
* resolve.
On Sun, 12 Mar 2017, Moore, Catherine wrote:
>> Okay to yank it?
> Yes, thank you.
Done per the patch below (committed).
> I will review the rest of the MIPS doc in install.texi this week.
Thank you!
Gerald
2017-03-12 Gerald Pfeifer
* doc/install.texi (Specific) : Remove descri
On Mon, Feb 27, 2017 at 6:15 AM, Janne Blomqvist
wrote:
> Don't try to use rand_s on CYGWIN
>
> CYGWIN seems to include _mingw.h and thus __MINGW64_VERSION_MAJOR is
> defined even though rand_s is not available. Thus add an extra check
> for __CYGWIN__.
>
> Thanks to Tim Prince and Nightstrike for
> -Original Message-
> From: Gerald Pfeifer [mailto:ger...@pfeifer.com]
> Sent: Sunday, March 12, 2017 7:38 AM
> To: gcc-patches@gcc.gnu.org; Moore, Catherine
> ; Matthew Fortune
>
> Subject: install.texi and mips-*-* (was: Target maintainers: doc/install.texi
> love and care)
>
> On Su
Committed, based on gcc-7/changes.html before that one is trimmed
down, with some changes to the intro, formatting (simpler),...
Gerald
PS: In a follow up commmit I added in the empty
environments.
Index: gcc-8/changes.html
===
R
On Thu, 9 Mar 2017, Thomas Preudhomme wrote:
JonY: what about the attached patch to document the change of behavior
of GCC on Windows depending on the configure option used?
+MinGW issues
+
+GCC on Microsoft Windows can now be configured via
+--enable-mingw-wildcard or --disable-mingw-wildcard
On Wed, 2017-03-08 at 09:05 -0500, Nathan Sidwell wrote:
> thanks. in case you'd not noticed Ian T's okayed my review. so this is
> good to go
Thanks. Markus pushed it including the testcases.
But there are still two testcase (not added, but attached below) that
are still failing (but now just
On Sun, 12 Mar 2017, Hans-Peter Nilsson wrote:
> Certainly! Thanks.
Done thusly; thanks for the quick response, H-P.
(May there be further changes to consider for cris-*?)
Gerald
2017-03-12 Gerald Pfeifer
* doc/install.texi (Specific) : No longer
refer to binutils 2.11/2.1
> Date: Sun, 12 Mar 2017 12:34:25 +0100 (CET)
> From: Gerald Pfeifer
> On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> > References to dependencies on really, really old versions of
> > binutils (talking 10+ years here) which I think we can remove.
> > Let me follow-up with some of you with concrete
Hi Jakub,
The Fortran FE registers its own format decoder, overriding the default
one that handles what the middle-end can emit, e.g.
warning (OPT_Wpadded, "padding struct to align %q+D", field);
The C/C++ FEs are the only other ones that override the decoder, but they
do handle all the specs th
The following is an *untested* patch suggestion, please verify.
Notes: My interpretation is that hash should be
defined outside of the _GLIBCXX_COMPATIBILITY_CXX0X block, please
double-check that course of action.
I noticed that the preexisting hash did directly refer to
the private members of er
Tested on Linux-x64.
2017-03-12 Ville Voutilainen
Implement LWG 2806, Base class of bad_optional_access.
* include/std/optional (bad_optional_access):
Derive from std::exception.
(bad_optional_access::bad_optional_access): Adjust.
(bad_optional_access::what): New.
(__th
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestions
> around that.
The section on sparc-*-linux* currently has this:
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestions
> around that.
The mips-*-* currently has this:
The assembler
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestions
> around that.
The i?86-*-linux* section currently has this:
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestions
> around that.
The cris-axis-elf / cris-axis-linux-gnu section c
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> Also, I'm offering help around one particular aspect I noticed:
>
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestio
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> Also, I'm offering help around one particular aspect I noticed:
>
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestio
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
> Also, I'm offering help around one particular aspect I noticed:
>
> References to dependencies on really, really old versions of
> binutils (talking 10+ years here) which I think we can remove.
> Let me follow-up with some of you with concrete suggestio
binutils is another GNU project (and well known and easy to obtain),
so linking to ftp.kernel.org feels a little surprising.
I simplified this and generally streamlined this note - which luckily
is a lot less necessary now then when it was added many moons ago.
In fact, do you think we can even
34 matches
Mail list logo
