Rainer Orth wrote:
Hi Pierre-Marie,
This fixes an issue when setting the baud rate. The baud rate is set
using the cfsetospeed and cfsetispeed system calls. The code is using
speed_t for clarity. The non-blocking status is only reset when Block is
True. And serial blocking mode is now
Thank you very much.
вт, 15 дек. 2020 г. в 12:48, Jonathan Wakely :
> On 10/12/20 18:39 +0100, Vladimir V via Libstdc++ wrote:
> >Hello.
> >
> >Could you please have a look at my trivial patch.
> >It works as intended with avr-libc and doesn't seem to introduce
> >regressions for x86_64 hosts.
>
If any ---checking options used
On 11/11/20 6:09 PM, Martin Sebor via Gcc-patches wrote:
> The attached patch builds on top of the series I posted last
> week(*) to improve the detection of out of bounds pointers
> and C++ references, as well as a subset of invalid pointer
> relational and subtraction expressions.
>
> First,
On 11/13/20 1:24 AM, Richard Sandiford via Gcc-patches wrote:
> This patch rewrites fwprop.c to use the RTL SSA framework. It tries
> as far as possible to mimic the old behaviour, even in caes where
> that doesn't fit naturally with the new framework. I've added ???
> comments to mark those
On 11/13/20 1:23 AM, Richard Sandiford via Gcc-patches wrote:
> This patch adds the RTL SSA infrastructure itself. The following
> fwprop.c patch will make use of it.
>
> gcc/
> * configure.ac: Add rtl-ssa to the list of dependence directories.
> * configure: Regenerate.
> *
On 12/15/20 10:30 AM, H.J. Lu wrote:
> Since SHF_GNU_RETAIN support doesn't work for crtstuff.c which switches
> the output section directly with asm statement:
>
> ---
> static void __attribute__((used))
> __do_global_dtors_aux (void)
> {
> static _Bool completed;
>
> if (__builtin_expect
On 12/15/20 10:30 AM, H.J. Lu wrote:
> When SECTION_RETAIN is used, issue a warning when a symbol without used
> attribute and a symbol with used attribute are placed in the section with
> the same name, like
>
> int __attribute__((used,section(".data.foo"))) foo2 = 2;
> int
On 12/15/20 10:30 AM, H.J. Lu wrote:
> When definitions marked with used attribute and unmarked definitions are
> placed in the section with the same name, switch to a new section if the
> SECTION_RETAIN bit doesn't match.
>
> gcc/
>
> PR target/98146
> * output.h
On 12/14/20 3:09 AM, Martin Liška wrote:
> On 12/10/20 4:50 PM, Martin Sebor wrote:
>> Most similar warnings mention the sanitizer option rather than
>> referring to the tool by name.  E.g.,
>>
>>    "transactional memory is not supported withÂ
>>
On 12/14/20 3:10 AM, Marius Hillenbrand via Gcc-patches wrote:
> Hi,
>
> Currently, when the option --enable-s390-excess-float-precision is
> omitted, configure checks the libc's behavior only for native builds yet
> defaults to the new model for cross compiles. This patch extends the
>
Hi,
This patch fixes an ICE in dwarf2out.c that occurs when compiling a
selective import declaration in D with strict dwarf2 in effect.
Manifest constants in D are represented as CONST_DECLs, which can be
imported from one module to another. However, when compiling on strict
dwarf2 targets such
On 12/15/20 3:17 AM, Eric Botcazou wrote:
>> OK.
> Thanks. Unfortunately I overlooked the comment of the function:
>
> MINVAL is the lowest case value of in the case nodes,
> and RANGE is highest value minus MINVAL. MINVAL and RANGE
> are not guaranteed to be of the same type as
On Tue, Dec 15, 2020 at 3:51 PM Ian Lance Taylor wrote:
>
> On Tue, Dec 15, 2020 at 3:43 PM Ian Lance Taylor wrote:
> >
> > I'm trying to commit a change that adds a bunch of new files to
> > gcc/testsuite/go.test/test. It's being rejected because the hook
> > can't deduce a ChangeLog file.
On Tue, Dec 15, 2020 at 3:43 PM Ian Lance Taylor wrote:
>
> I'm trying to commit a change that adds a bunch of new files to
> gcc/testsuite/go.test/test. It's being rejected because the hook
> can't deduce a ChangeLog file. But this directory has no ChangeLog
> files. I've committed other
I'm trying to commit a change that adds a bunch of new files to
gcc/testsuite/go.test/test. It's being rejected because the hook
can't deduce a ChangeLog file. But this directory has no ChangeLog
files. I've committed other changes to this directory without a
ChangeLog entry.
What is going
It turned out that r11-5942 fixed this old PR, and it was detected
by one of the few dg-ice tests -- exactly the point of them! Now
the PR won't be opened until someone notices that it'd been fixed.
The patch failed to remove the dg-ice though, so now it XPASSes. Fixing
this now.
Tested
On 12/15/20 3:30 AM, Martin Liška wrote:
> The patch reports an error when a non-HOST_WIDE_INT options is used
> and its value is bigger than INT_MAX.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
>
On 12/15/20 1:38 PM, Maciej W. Rozycki wrote:
> Complement commit 20ab43b5cad6 ("RTL: Add `const_double_zero' syntactic
> rtx") and remove a commit c60d0736dff7 ("PDP11: Use `const_double_zero'
> to express double zero constant") build regression observed with the
> `pdp11-aout' target:
>
>
On Tue, 15 Dec 2020 18:00:36 +0100
Jakub Jelinek wrote:
> On Tue, Dec 15, 2020 at 04:49:38PM +, Julian Brown wrote:
> > > Do you need to hold the omp_stacks.lock across the entire
> > > offloading? Doesn't that serialize all offloading kernels to the
> > > same device? I mean, can't the lock
Hi Pierre-Marie,
> This fixes an issue when setting the baud rate. The baud rate is set
> using the cfsetospeed and cfsetispeed system calls. The code is using
> speed_t for clarity. The non-blocking status is only reset when Block is
> True. And serial blocking mode is now properly set according
Hi Nathan,
> as expected there are a bunch of configurey type errors. I am aware of the
> following:
[...]
> solaris 11, sys/socket.h, bcopy and poisoning. Asked jwakely to try a
> patch, he seems to have a build set up.
two more Solaris issues (will file proper PRs tomorrow):
* Solaris 11.4
as expected there are a bunch of configurey type errors. I am aware of
the following:
windows build (pr 98300), insufficient #ifing. A patch is being tested
solaris 11, sys/socket.h, bcopy and poisoning. Asked jwakely to try a
patch, he seems to have a build set up.
AIX install. Testing
Tested x86_64-pc-linux-gnu, applying to trunk.
libcody/ChangeLog:
* buffer.cc (MessageBuffer::Lex): Remove unused variable.
---
libcody/buffer.cc | 1 -
1 file changed, 1 deletion(-)
diff --git a/libcody/buffer.cc b/libcody/buffer.cc
index 52df3176c9a..3256c37399b 100644
---
Richard,
> Do we already handle x < y || x <= CST to x <= y - CST?
That is an invalid transformation: e.g., consider x=3, y=4, CST=2.
Can you please clarify?
Thanks,
Eugene
-Original Message-
From: Richard Biener
Sent: Thursday, December 10, 2020 12:21 AM
To: Eugene Rozenfeld
Cc:
On Thu, Nov 19, 2020 at 07:16:52PM +, Jonathan Wakely wrote:
> On 19/11/20 12:57 -0500, Lewis Hyatt via Libstdc++ wrote:
> > Hello-
> >
> > PR61369 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61369) points out
> > that std::discrete_distribution can return an event even if it has 0
> >
I missed adding these two configure files.
gcc_update: Add c++tools & libcody
thanks David for pointing at the fix.
nathan
--
Nathan Sidwell
>From c6d406f5039072938d308fe3a7fc4cd2a0bac952 Mon Sep 17 00:00:00 2001
From: Nathan Sidwell
Date: Tue, 15 Dec 2020 13:42:23 -0800
Subject:
Older GCCs don't have all the exciting options we have now. let's just
turn them off.
Makefile.in: Disable some flags
--
Nathan Sidwell
>From 98b960b40ba4934bdbd8d87d9432475e148d1022 Mon Sep 17 00:00:00 2001
From: Nathan Sidwell
Date: Tue, 15 Dec 2020 13:34:26 -0800
Subject:
Hi,
This patch fixes an ICE during gimplify_expr for code generated by the D
front-end. The DMD front-end shouldn't, but can sometimes leak manifest
constants in the AST passed to the code generator. To prevent this
being an issue, the setting of DECL_INITIAL has been moved to the point
where
On Tue, Dec 15, 2020 at 1:01 PM Ian Lance Taylor wrote:
>
> This patch to the Go frontend avoids knock-on errors from invalid
> interfaces. The test case for this is issue11614.go in the source
> repo. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
> Committed to mainline.
Sorry, I
This patch to the Go frontend corrects the grammar in an error
message. Noticed while looking at https://golang.org/issue/43200.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
5aba02667113fbe43d74c37724f29868f098dd1c
diff --git a/gcc/go/gofrontend/MERGE
This patch to the Go frontend avoids knock-on errors from invalid
interfaces. The test case for this is issue11614.go in the source
repo. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
788d204885c187d5604e3960d7c78e1523f04861
diff --git
Dear all,
ICE-on-invalid: testcase by Arseny, draft patch by Steve,
slightly polished and regtested by me on x86_64-pc-linux-gnu.
OK for master?
Thanks,
Harald
PR fortran/98284 - ICE in get_array_index
Reject DATA elements with the ALLOCATABLE attribute also when they are
components of a
This patch to the Go frontend discards global sink variables with
static initializers. This is specifically for the test issue23781.go,
which builds a large static array. The code does compile and work
without this change, but it takes a long time and generates a large
object file. Discarding
This patch to the Go frontend generates a better error for an
unexpected digit. A digit character is not invalid in general, but
it's not permitted at the start of an identifier. Report a better
error message. The test case is issue11359.go in the source repo.
Bootstrapped and ran Go testsuite
On Wed, Dec 02, 2020 at 05:15:21AM -0800, H.J. Lu via Gcc-patches wrote:
> gcc/
>
> PR middle-end/93195
> PR middle-end/93197
> * configure.ac (HAVE_GAS_SECTION_LINK_ORDER): New. Define 1 if
> the assembler supports the section flag 'o' for specifying
> section with
On 12/15/20 7:30 AM, Segher Boessenkool wrote:
> On Tue, Dec 15, 2020 at 08:40:08AM +0100, Gerald Pfeifer wrote:
>> On Mon, 6 Jan 2020, Jeff Law wrote:
p.s. You know anything about Denis Chertykov? He used to reply to avr
patches within hours, but my latest patches (after a long
Complement commit 20ab43b5cad6 ("RTL: Add `const_double_zero' syntactic
rtx") and remove a commit c60d0736dff7 ("PDP11: Use `const_double_zero'
to express double zero constant") build regression observed with the
`pdp11-aout' target:
genemit: Internal error: abort in gen_exp, at genemit.c:202
On Linux/x86_64,
cf4ed3b41594b6935a337fe0aaf8149eadf88751 is the first bad commit
commit cf4ed3b41594b6935a337fe0aaf8149eadf88751
Author: Jonathan Wakely
Date: Tue Dec 15 11:40:06 2020 +
libstdc++: Use init_priority attribute for Init object [PR 98108]
caused
FAIL:
Hi Richard,
Here's the split off complex add.
Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
Checked with armv8-a+sve2+fp16 and no issues. Note that due to a mid-end
limitation SLP for SVE currently fails for some permutes. The tests have these
marked as XFAIL.
Matching tests
On 12/15/20 1:02 AM, Martin Liška wrote:
> I've tested this mechanical change for all cross compilers.
>
> Ready to be installed?
ENOPATCH, but same as 1/1 of this series. OK by me given I can guess
what it looks like, but give Jakub and Richi time to chime in.
jeff
On 12/15/20 1:01 AM, Martin Liška wrote:
> There's a small clean up that removes Report as it's not used
> any longer by -fverbose-asm.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
Apparently 'var+=...' is not a dash thing. Fixed thusly.
* config.m4: Avoid non-dash idiom
* configure: Rebuilt.
pushed (2 patches, because I didn't look carefully enough the first time)
--
Nathan Sidwell
diff --git i/libcody/config.m4 w/libcody/config.m4
index
On 12/15/20 2:05 AM, Jakub Jelinek wrote:
> Hi!
>
> When the divisor is bool or has [0, 1] range, as division by
> 0 is UB, the only remaining option in valid programs is division by 1,
> so we can optimize X / bool_range_Y into X.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok
On 15/12/20 11:47 +, Jonathan Wakely wrote:
This causes the global objects that run the initialization
code to be constructed earlier, which avoids some bugs in user code due
to incorrectly relying on static initialization order.
libstdc++-v3/ChangeLog:
PR libstdc++/98108
On 10/12/20 12:56 -0800, Keith Packard via Libstdc++ wrote:
Jonathan Wakely writes:
I'll do a bit more testing and push it next week.
That's awesome news. Thanks so much for you help; I'm looking forward to
having real C++ support for my embedded customers!
Pushed to master.
commit
On Tue, 15 Dec 2020, Paul Koning wrote:
> > I'm fairly sure this is due to the difference in TARGET_SUPPORTS_WIDE_INT
> > with the VAX backend vs the PDP-11 one. I have an idea how this should be
> > addressed and will be implementing it shortly.
>
> What's the difference? pdp11 does support
> On Dec 15, 2020, at 9:06 AM, Maciej W. Rozycki wrote:
>
> On Tue, 15 Dec 2020, Martin Liška wrote:
>
>> If I see correctly, starting from this revision I can't compile a cross
>> compiler of x86_64-linux-gnu:
>>
>> ../configure --target=pdp11-aout --disable-bootstrap
When definitions marked with used attribute and unmarked definitions are
placed in the section with the same name, switch to a new section if the
SECTION_RETAIN bit doesn't match.
gcc/
PR target/98146
* output.h (switch_to_section): Add a tree argument, default to
When SECTION_RETAIN is used, issue a warning when a symbol without used
attribute and a symbol with used attribute are placed in the section with
the same name, like
int __attribute__((used,section(".data.foo"))) foo2 = 2;
int __attribute__((section(".data.foo"))) foo1 = 1;
since assembler will
Since SHF_GNU_RETAIN support doesn't work for crtstuff.c which switches
the output section directly with asm statement:
---
static void __attribute__((used))
__do_global_dtors_aux (void)
{
static _Bool completed;
if (__builtin_expect (completed, 0))
return;
completed = 1;
}
static
When SECTION_RETAIN is used, definitions marked with used attribute and
unmarked definitions are placed in a section with the same name. Instead
of issue an error:
[hjl@gnu-cfl-2 gcc]$ /usr/gcc-11.0.0-x32/bin/gcc -S c.c
-fdiagnostics-plain-output
c.c:2:49: error: ‘foo1’ causes a section type
On Thu, Oct 29, 2020 at 12:11 PM H.J. Lu wrote:
>
> Add the --enable-pgo-build[=lto] configure option. When binutils+gdb
> is not built together with GCC, --enable-pgo-build enables the PGO build:
>
> 0. Pass --plugin to AR and RANLIB.
> 1. First build with -fprofile-generate.
> 2. Use "make
On Mon, Dec 14, 2020 at 11:58:05PM +, Joseph Myers wrote:
> > Thanks for heads up. I'm aware of it and I don't see reason why (running the
> > update script in dry mode works).
>
> https://gcc.gnu.org/pipermail/gccadmin/2020q4/017037.html
>
> OSError: [Errno 28] No space left on device:
>
On Tue, Dec 15, 2020 at 04:49:38PM +, Julian Brown wrote:
> > Do you need to hold the omp_stacks.lock across the entire offloading?
> > Doesn't that serialize all offloading kernels to the same device?
> > I mean, can't the lock be taken just shortly at the start to either
> > acquire the
On Tue, 15 Dec 2020 14:49:40 +0100
Jakub Jelinek wrote:
> On Tue, Dec 15, 2020 at 01:39:13PM +, Julian Brown wrote:
> > @@ -1922,7 +1997,9 @@ GOMP_OFFLOAD_run (int ord, void *tgt_fn, void
> > *tgt_vars, void **args) nvptx_adjust_launch_bounds (tgt_fn,
> > ptx_dev, , );
> >size_t
Am 13.12.20 um 20:59 schrieb Iain Sandoe via Fortran:
For bonus points you can prefix with _GFC_ which puts the symbols
in the implementation’s namespace (at least for C-Family purposes)
and therefore means that a clash with a user’s symbols is the user’s
problem …
I don't think this is
I've completed merging modules to trunk modulo the testsuite. I
included a few smoke tests, but nothing more. I'll add the rest when
the smoke clears.
There will undoubtedly be issues related to configs that I've not built.
As I mentioned I did what I could.
Further, it'll undoubtedly
And here is the user-facing documentation.
gcc/
* doc/cppopts.texi: Document new cpp opt.
* doc/invoke.texi: Add C++20 module option & documentation.
--
Nathan Sidwell
diff --git c/gcc/doc/cppopts.texi w/gcc/doc/cppopts.texi
index 7f1849d841f..e5ece92487b
To avoid always requiring an active mapper to connect to, we provide a
default in-process mapper with similar functionality to the sample
server. This is that code. Also included is the client-side connection
mechanism, which determines what server to use and how to
connect to it.
These tests FAIL when testing debug mode with a small tool_timeout
value. Give them a longer relative timeout.
libstdc++-v3/ChangeLog:
* testsuite/25_algorithms/lexicographical_compare/deque_iterators/1.cc:
Add dg-timeout-factor directive.
*
On 15/12/20 15:20 +, Jonathan Wakely wrote:
On 14/12/20 22:36 +0100, François Dumont wrote:
On 14/12/20 11:08 am, Jonathan Wakely wrote:
On Mon, 14 Dec 2020, 06:51 François Dumont via Libstdc++,
mailto:libstdc%2b...@gcc.gnu.org>> wrote:
On 13/12/20 11:17 pm, Jonathan Wakely wrote:
On 14/12/20 22:36 +0100, François Dumont wrote:
On 14/12/20 11:08 am, Jonathan Wakely wrote:
On Mon, 14 Dec 2020, 06:51 François Dumont via Libstdc++,
mailto:libstdc%2b...@gcc.gnu.org>> wrote:
On 13/12/20 11:17 pm, Jonathan Wakely wrote:
> On 13/12/20 15:52 +0100, François Dumont
Add toplevel dirs
contrib/
* gcc-changelog/git_commit.py (changelog_locations): Add
libcody, c++tools.
pushed to trunk
--
Nathan Sidwell
diff --git c/contrib/gcc-changelog/git_commit.py w/contrib/gcc-changelog/git_commit.py
index 0c438165516..01f49874652
Hi Ke Wen,
On Tue, Dec 15, 2020 at 03:53:29PM +0800, Kewen.Lin wrote:
> on 2020/12/15 上午2:51, Segher Boessenkool wrote:
> > On Wed, Dec 02, 2020 at 05:44:24PM +0800, Kewen.Lin wrote:
> >> --- a/gcc/config/rs6000/rs6000.c
> >> +++ b/gcc/config/rs6000/rs6000.c
> >> @@ -6793,17 +6793,8 @@
On Tue, Dec 15, 2020 at 08:40:08AM +0100, Gerald Pfeifer wrote:
> On Mon, 6 Jan 2020, Jeff Law wrote:
> >> p.s. You know anything about Denis Chertykov? He used to reply to avr
> >> patches within hours, but my latest patches (after a long period where I
> >> didn't propose any patches) where
On Tue, 15 Dec 2020, Martin Liška wrote:
> If I see correctly, starting from this revision I can't compile a cross
> compiler of x86_64-linux-gnu:
>
> ../configure --target=pdp11-aout --disable-bootstrap --enable-languages=c,c++
> --disable-multilib --enable-obsolete
Thanks for the heads-up
On Tue, Dec 15, 2020 at 01:39:13PM +, Julian Brown wrote:
> @@ -1922,7 +1997,9 @@ GOMP_OFFLOAD_run (int ord, void *tgt_fn, void
> *tgt_vars, void **args)
>nvptx_adjust_launch_bounds (tgt_fn, ptx_dev, , );
>
>size_t stack_size = nvptx_stacks_size ();
> - void *stacks =
On Tue, 8 Dec 2020 20:11:38 +0300
Alexander Monakov wrote:
> On Tue, 8 Dec 2020, Julian Brown wrote:
>
> > Ping?
>
> This has addressed my concerns, thanks.
Jakub, Tom -- just to confirm, is this OK for trunk now?
I noticed a slight bugfix myself in the no-stacks/out-of-memory case --
i.e.
Reported-by: Heinrich Schuchardt
Signed-off-by: Alejandro Colomar
Cc: Martin Sebor
Cc: Dave Martin
---
v6:
- GCC has always exposed 'void *', as Martin Sebor noted.
It's Clang (and maybe others) that (following GCC's docs)
exposed 'char *'.
man2/cacheflush.2 | 24
Now that the G++ bug is fixed we no longer need to protect this partial
specialization from complaining about subtracting void pointers.
libstdc++-v3/ChangeLog:
* include/bits/iterator_concepts.h (incrementable_traits):
Remove workaround for PR c++/78173.
Tested
On 10/12/20 18:39 +0100, Vladimir V via Libstdc++ wrote:
Hello.
Could you please have a look at my trivial patch.
It works as intended with avr-libc and doesn't seem to introduce
regressions for x86_64 hosts.
I've pushed this to master now, thanks for the patch.
What would be your
This causes the global objects that run the initialization
code to be constructed earlier, which avoids some bugs in user code due
to incorrectly relying on static initialization order.
libstdc++-v3/ChangeLog:
PR libstdc++/98108
* include/std/iostream (__ioinit): Add
This fixes an issue when setting the baud rate. The baud rate is set
using the cfsetospeed and cfsetispeed system calls. The code is using
speed_t for clarity. The non-blocking status is only reset when Block is
True. And serial blocking mode is now properly set according to termios
manual.
Add
This patch fixes an issue in the compiler whereby postconditions were
incorrectly checked prior to the execution of finalization.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* contracts.adb, contracts.ads (Build_Postconditions_Procedure):
Add declarations for
Refactor repeated code in the parser for complaining about a missing
-gnat2005 switch. Fix singular-vs-plural phrasing.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* errout.ads (Error_Msg_Ada_2005_Extension): New routine (spec).
* errout.adb
Reuse Error_Msg_Ada_2020_Feature to complain about a missing -gnat2020
switch when compiling iterator_filter that would be legal in Ada 2020,
but the compiler is expecting an earlier version of the language.
A small enhancement; opportunity spotted while adding support for
iterator filters in
This changes the implementation of input operations for floating-point
types from using Long_Long_Float for all floating-point types to using
a base type tailored to the type being operated on.
This comprises adjusting Ada.Text_IO.Float_IO and Ada.Text_IO.Complex_IO
to the new approach, as well
This changes Precision_Limit from being computed based on the unsigned
type to being explicitly specified in the instantiation, and restores
its value to the precision of the mantissa for floating-pointt types.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
This recovers a few bits of precision by always using the Extra digit.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/s-valrea.adb (Integer_to_Real): Always use Extra.diff --git a/gcc/ada/libgnat/s-valrea.adb b/gcc/ada/libgnat/s-valrea.adb
---
New body for Ada.Text_IO.Float_IO makes explicit use of Long_Long_Float
which is not supported by GNATprove for now. Exclude that generic body
from SPARK explicitly so that the unit can be instantiated from SPARK
code.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
As shown by ACATS c74209a, there are remaining cases where the
Transform_Function_Array does not trigger properly, related to private
types on one hand, and to freezing of function with no separate spec on
the other hand.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
Relational operations on Uint are overloaded to accept Int as one of the
operands. There is no need to explicitly convert such operands with
UI_To_Int. Cleanup only; semantics is unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_disp.adb (Make_Tags): Remove
As seen on e.g. ACATS ca5006a when front-end unnesting is enabled.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_ch7.adb (Reset_Scopes_To_Block_Elab_Proc): Do not crash on
a block with no Identifier. Code cleanups.diff --git a/gcc/ada/exp_ch7.adb
When the directory iterator Find is called we need to ensure that
symbolic links are skipped to avoid possible circularities or exploring
unrelated directories.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/g-diopit.adb (Find): Fix possible infinite recursion
Check related to restriction No_Enumeration_Maps and marking enumeration
literals as referenced were done to attribute Value in both compilation
and semantic checking mode (-gnatc), but to attributes Wide_Value and
Wide_Wide_Value only in compilation (because those attributes are
rewritten into
On Tue, Dec 15, 2020 at 12:48:47AM +0100, Gerald Pfeifer wrote:
> On Mon, 7 Dec 2020, Jozef Lawrynowicz wrote:
> > Committed as obvious.
>
> Thank you!
>
> +
> +For ELF targets that support the GNU or FreeBSD OSABIs, the
> +used attribute will now save the symbol declaration it is
> +
On Tue, Dec 15, 2020 at 06:10:57PM +0800, Hongtao Liu via Gcc-patches wrote:
> --- a/gcc/config/i386/i386.c
> +++ b/gcc/config/i386/i386.c
> @@ -18187,21 +18187,67 @@ ix86_gimple_fold_builtin (gimple_stmt_iterator *gsi)
> }
>break;
>
> +case IX86_BUILTIN_SHUFPD512:
> +case
On 15/12/20 12:13 +0200, Ville Voutilainen via Libstdc++ wrote:
libstdc++-v3/ChangeLog:
* testsuite/27_io/rvalue_streams.cc: Run the extraction to a char*
for C++17 and lower only.
OK, thanks.
diff --git a/libstdc++-v3/testsuite/27_io/rvalue_streams.cc
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/gcc10/standard/ppc
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/gcc10/standard/ppc64
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552
The patch reports an error when a non-HOST_WIDE_INT options is used
and its value is bigger than INT_MAX.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
PR rtl-optimization/98271
PR
On 14/12/20 11:19 +0100, Marius Hillenbrand wrote:
I'd like to ping the small fixup in
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/560100.html
Please review and merge, if OK.
Patches for libstdc++ need to be CC'd to the libstdc++ list, or I
won't see them (this is mentioned at
On Tue, Dec 15, 2020 at 11:10:17AM +0100, Eric Botcazou wrote:
> > Similarly for sparc,
> > --build=sparc64-redhat-linux --target=sparc64-redhat-linux --with-cpu=v7
> > was the bi-arch compiler with 32-bit binaries that defaults to -m32, but
> > also supports -m64, while
> >
> OK.
Thanks. Unfortunately I overlooked the comment of the function:
MINVAL is the lowest case value of in the case nodes,
and RANGE is highest value minus MINVAL. MINVAL and RANGE
are not guaranteed to be of the same type as INDEX_EXPR
(the gimplifier doesn't change the type
libstdc++-v3/ChangeLog:
* testsuite/27_io/rvalue_streams.cc: Run the extraction to a char*
for C++17 and lower only.
diff --git a/libstdc++-v3/testsuite/27_io/rvalue_streams.cc b/libstdc++-v3/testsuite/27_io/rvalue_streams.cc
index ad4d11c7cf3..487aa4deedd 100644
---
> Yeah, it is the same thing for Fedora/RHEL when we were supporting -m32
> for powerpc.
> The bi-arch compiler with 32-bit binaries that defaults to -m32, but also
> supports -m64 was configured
> --build=powerpc64-redhat-linux --target=powerpc64-redhat-linux
> --with-cpu=default32 while the
Hi:
As indicated in PR98167, this patch is a follow-up to [1].
Bootstrapped and regtested on x86_64-linux-gnu.
Ok for trunk?
gcc/
PR target/98167
* config/i386/i386.c (ix86_gimple_fold_builtin): Handle
IX86_BUILTIN_SHUFPD512, IX86_BUILTIN_SHUFPS512,
Vladimir Makarov writes:
> On 2020-12-14 11:23 a.m., Andrea Corallo wrote:
>> Vladimir Makarov writes:
>>
>>> On 2020-12-10 10:12 a.m., Andrea Corallo wrote:
Hi all,
following discussion on PR97092 I'd like to submit the following patch
with a fix plus associated testcase.
On Tue, Dec 15, 2020 at 10:54:47AM +0100, Andreas Schwab wrote:
> On Dez 15 2020, Eric Botcazou wrote:
>
> > The two assertions cannot possibly be true at the time.
>
> But they are.
Yeah, it is the same thing for Fedora/RHEL when we were supporting -m32
for powerpc.
The bi-arch compiler with
On Dez 15 2020, Eric Botcazou wrote:
> The two assertions cannot possibly be true at the time.
But they are.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
1 - 100 of 115 matches
Mail list logo
