This is a new one.
http://www.microchip.com/design-centers/8-bit/microchip-avr-mcus
2018-03-10 20:15 GMT+04:00 Gerald Pfeifer :
> It appears this link at atmel.com has been taken down without
> what appears a replacement, so I applied the patch below.
>
> Denis, if you have a new reference, happy
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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/gcc/es.po
(This file, 'gcc-8.1-b20180128.es.po',
On Mon, Mar 5, 2018 at 4:17 AM, H.J. Lu wrote:
> On Mon, Feb 26, 2018 at 12:48 PM, H.J. Lu wrote:
>> Function return thunks shouldn't be aliased to indirect branch thunks
>> since indirect branch thunks are placed in COMDAT section and a COMDAT
>> section with indirect branch may not have functio
On Mon, Mar 5, 2018 at 4:20 AM, H.J. Lu wrote:
> On Tue, Feb 27, 2018 at 11:39 AM, H.J. Lu wrote:
>> For x86 targets, when -fno-plt is used, external functions are called
>> via GOT slot, in 64-bit mode:
>>
>> [bnd] call/jmp *foo@GOTPCREL(%rip)
>>
>> and in 32-bit mode:
>>
>> [bnd
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 Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-8.1-b20180128.sv.po',
Avoid issuing a bogus warning when the source of strncpy is bound by a
constant and is known to be less than the size of the destination.
Testsuite run is underway (not complete yet, but no new errors so far)
and a bootstrap is also underway, I'll report status once they're both
done.
gcc/
PR83789 shows a problem in the builtin expansion code not calling the correct
define_insn, given the correct mode (32-bit versus 64-bit). One could add
tests in this code to call the correct pattern, but it's easier to create
a common define_expand which everyone can call that does the right thing
OK.
On Fri, Mar 9, 2018 at 1:15 PM, Jakub Jelinek wrote:
> Hi!
>
> As the following testcase shows, we emit bad debug info if a scoped
> enum is used before the enumerators are defined.
> gen_enumeration_type_die has support for enum forward declarations that
> have NULL TYPE_SIZE (i.e. incomplet
The attach patch cleans up KILL to match its
documentation. In doing so, I have changed
the argument keywords to consistently use
pid and sig. If no one objects, I intend to
commit this tomorrow.
2018-03-11 Steven G. Kargl
* check.c (gfc_check_kill): Check pid and sig are scalar.
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-8.1-b20180128.de.po', h
Applied.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.290
diff -u -r1.290 readings.html
--- readings.html 10 Mar 2018 16:15:35 - 1.290
+++ readings.html
It appears I already fixed this weeks, if not months ago, except
that actually committing the changes helps?
Done now.
Gerald
Index: projects/prefetch.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/prefetch.html,v
retrieving re
This regression came about because the vtable deep copy for derived
types with unlimited polymorphic components was not making use of the
_len parameter to compute the memory to be allocated and the offsets
to array elements.
The ChangeLogs are reasonably self explanatory.
Bootstraps and regtests
On 03/11/2018 12:23 PM, Paul Richard Thomas wrote:
This regression came about because the vtable deep copy for derived
types with unlimited polymorphic components was not making use of the
_len parameter to compute the memory to be allocated and the offsets
to array elements.
The ChangeLogs are
Hello world,
the attached patch fixes a few corner cases of a corner case in
simplification, i.e. empty arrays where array intrinsics can actually
have a non-empty array result.
Regression-tested. OK for trunk?
Regards
Thomas
2017-06-11 Thomas Koenig
PR fortran/66128
On Sun, Mar 11, 2018 at 6:52 PM, Steve Kargl
wrote:
> The attach patch cleans up KILL to match its
> documentation. In doing so, I have changed
> the argument keywords to consistently use
> pid and sig. If no one objects, I intend to
> commit this tomorrow.
>
> 2018-03-11 Steven G. Kargl
>
>
On Sun, Mar 11, 2018 at 9:55 PM, Thomas Koenig wrote:
> Hello world,
>
> the attached patch fixes a few corner cases of a corner case in
> simplification, i.e. empty arrays where array intrinsics can actually
> have a non-empty array result.
>
> Regression-tested. OK for trunk?
Looks good, Ok.
On Sun, Mar 11, 2018 at 10:16:01PM +0200, Janne Blomqvist wrote:
> On Sun, Mar 11, 2018 at 6:52 PM, Steve Kargl
> wrote:
> > The attach patch cleans up KILL to match its
> > documentation. In doing so, I have changed
> > the argument keywords to consistently use
> > pid and sig. If no one object
The attach patch enforces F2018:C15100. Similar constraints are
present in older versions of the standard. The patch and testcase
are sufficiently explanatory. Regression tested on x86_64-*-freebsd.
OK to commit?
2018-03-11 Steven G. Kargl
PR fortran/83939
* resolve.c (reso
On Fri, Mar 9, 2018 at 10:51 PM, Bin.Cheng wrote:
> On Fri, Mar 9, 2018 at 10:25 AM, Paul Hua wrote:
>> It's looks fixed
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82965#c12 on mips64el.
> Hmm, is it fixed? or is it exposed now on mips64el? I read the latter
> from the comment.
It is fixe
On 03/11/2018 01:48 PM, Steve Kargl wrote:
The attach patch enforces F2018:C15100. Similar constraints are
present in older versions of the standard. The patch and testcase
are sufficiently explanatory. Regression tested on x86_64-*-freebsd.
OK to commit?
Looks OK Steve.
Jerry
2018-03-
21 matches
Mail list logo
