Hi,
Compare with previous version, this patch updates the comments only.
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608293.html
For a complicate 64bit constant, below is one instruction-sequence to
build:
lis 9,0x800a
ori 9,9,0xabcd
sldi 9,9,32
oris
Hi,
"ilp32" is used in these test cases to make sure test cases only run on a
32-bit environment. Unfortunately, these cases also run with
"-m32/-mpowerpc64" which causes unexpected errors. This patch changes the
target check to skip if "has_arch_ppc64" is set. So the test cases won't run
when
Hi,
This patch changes the mode of exponent to GPR in scalar insert exp
pattern, as the exponent can be put into a 32-bit register. Also the
condition check is changed from TARGET_64BIT to TARGET_POWERPC64.
The test cases are modified according to the changes of expand pattern.
Hi,
This patch changes the return type of __builtin_vsx_scalar_extract_sig
from const signed long to const signed long long, so that it can be called
with "-m32/-mpowerpc64" option. The bif needs TARGET_POWERPC64 instead of
TARGET_64BIT. So the condition check in the expander is changed.
The
Hi,
This patch changes the return type of __builtin_vsx_scalar_extract_exp
from const signed long to const signed int, as the exponent can be put in
a signed int. It is also inline with the external interface definition of
the bif. The mode of exponent operand in "xsxexpdp" is changed to GPR
Hi,
I would like to have a ping on this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608292.html
BR,
Jeff (Jiufu)
Jiufu Guo writes:
> Hi,
>
> For constant C:
> If '(c & 0xULL) == 0x' or say:
> 32(1) || 1(0) || 15(x) || 16(0), we could use
Link is missing from install documentation
---
gcc/doc/install.texi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index ccc8d15fd08..18e8709a169 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -396,7 +396,8 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106680
Kewen Lin changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
On 1/2/23 03:20, Tobias Burnus wrote:
On 25.11.22 03:13, Sandra Loosemore wrote:
This patch is a followup to my not-yet-reviewed patch
[PATCH v4] OpenMP: Generate SIMD clones for functions with "declare
target"
That patch got reviewed and went into mainline on Nov 15, 2022 as
libiberty/ChangeLog:
* unlink-if-ordinary.c (unlink_if_ordinary):
Handle Windows nul device
---
libiberty/unlink-if-ordinary.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/libiberty/unlink-if-ordinary.c b/libiberty/unlink-if-ordinary.c
index 84328b216..ae9090e54
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108282
Martin Turski changed:
What|Removed |Added
CC||turningtides at outlook dot de
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108260
Jiang An changed:
What|Removed |Added
CC||de34 at live dot cn
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108282
Bug ID: 108282
Summary: Disabled template method using requires-clause still
viable through requires-expression
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108182
--- Comment #4 from Gaius Mulley ---
Created attachment 54184
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54184=edit
Potential fix for target multilib_dir handling -m and -f.
Work in progress.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
--- Comment #2 from Andrew Pinski ---
Note the original testcase does (inside _M_max_size):
return std::size_t(0x7fffL) / sizeof(_Tp);
Which was reduced to just:
attach___trans_tmp_3 = 9223372036854775807 / 2;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108280
Andrew Pinski changed:
What|Removed |Added
Component|lto |testsuite
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108281
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Component|target
On Wed, Dec 21, 2022 at 09:40:24PM +, Joseph Myers wrote:
> On Wed, 21 Dec 2022, Segher Boessenkool wrote:
>
> > > --- a/gcc/tree.cc
> > > +++ b/gcc/tree.cc
> > > @@ -9442,15 +9442,6 @@ build_common_tree_nodes (bool signed_char)
> > >if (!targetm.floatn_mode (n, extended).exists ())
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105010
--- Comment #20 from Segher Boessenkool ---
(In reply to Segher Boessenkool from comment #18)
> But! We do not support 2.00 at all since quite a while (-mcpu=power4
> does not mean 2.00, it means 2.02, i.e. POWER4+ actually), so this macro
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108281
--- Comment #1 from Alexander Kleinsorge ---
(same for types double and long-double)
> On 3 Jan 2023, at 22:22, Jason Merrill wrote:
>
> On 12/7/22 10:39, Iain Sandoe wrote:
>> This has been tested on x86_64 and arm64 Darwin and on x86_64 linux gnu.
>> The basic patch is live in the homebrew macOS support and so has had quite
>> wide coverage on non-trivial codebases.
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108281
Bug ID: 108281
Summary: float value range estimation missing (vs. integer)
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108280
Bug ID: 108280
Summary: [10 regression] Many lto excess errors after
r10-11132-gf543f71c54be74
Product: gcc
Version: 10.4.1
Status: UNCONFIRMED
Severity:
Source: gcc-11
Version: 11.3.0-10
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Affects: gcc-11, gcc-snapshot
X-Debbugs-CC: debian-h...@lists.debian.org
Hi,
gcc-11-11.3.0-10 in sid FTBFS on hurd-i386 due to failing linkage of
pthread_once (same error already
Source: gcc-11
Version: 11.3.0-10
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Affects: gcc-11, gcc-snapshot
X-Debbugs-CC: debian-h...@lists.debian.org
Hi,
gcc-11-11.3.0-10 in sid FTBFS on hurd-i386 due to failing linkage of
pthread_once (same error already
On 12/7/22 10:39, Iain Sandoe wrote:
This has been tested on x86_64 and arm64 Darwin and on x86_64 linux gnu.
The basic patch is live in the homebrew macOS support and so has had quite
wide coverage on non-trivial codebases.
OK for master?
Iain
Since this actually fixes wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
--- Comment #1 from David Binderman ---
Reduced C++ code is
typedef int mbstate_t;
namespace std {
struct Trans_NS___cxx11_basic_string {
char *c_str();
};
template _Facet use_facet(int);
template struct __codecvt_abstract_base {
typedef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108236
--- Comment #2 from Jakub Klinkovský ---
I copy-pasted this report in https://github.com/llvm/llvm-project/issues/59810
On Tue, 3 Jan 2023, Iain Sandoe wrote:
> 1. Modula-2 should not forward the builtins unless the target supports them,
> either by expansion or the relevant lib functions. So that would need
> some
>configury and conditional build code.
Note that such configure tests could only readily
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108182
--- Comment #3 from Gaius Mulley ---
I believe I have a fix for the target options. I've built gm2 as a cross
compiler for the avr series of microprocessors with the fix and now get a
cc1gm2 ICE (after the correct arguments are presented to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108279
--- Comment #1 from Thomas Koenig ---
Created attachment 54183
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54183=edit
Example patch with Michael S's code just pasted over the libgcc implementation,
for a test
A benchmarks: Just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108279
Bug ID: 108279
Summary: Improved speed for float128 routines
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92336
Gaius Mulley changed:
What|Removed |Added
CC||gaius at gcc dot gnu.org
--- Comment #4
Thanks Joseph,
> On 3 Jan 2023, at 18:15, Joseph Myers wrote:
>
> On Sat, 31 Dec 2022, Iain Sandoe wrote:
>
>> builtins.def unconditionally defines these builtins to be DEF_EXT_LIB_BUILTIN
>> which expands to the libcall, this is currently hard-wired to FALLBACK_P =
>> true.
>>
>> but, AFAIU
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
Bug ID: 108278
Summary: runtime error with -O1 -Wall
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
>
> On Tue, 3 Jan 2023, Jan Hubicka wrote:
>
> > > * gcc/common/config/i386/i386-common.cc (processor_alias_table):
> > > Use CPU_ZNVER4 for znver4.
> > > * config/i386/i386.md: Add znver4.md.
> > > * config/i386/znver4.md: New.
> > OK,
> > thanks!
>
> Honza, I'm curious what are your
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103760
Patrick Palka changed:
What|Removed |Added
CC||avr5309 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108254
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
On Sat, 31 Dec 2022, Iain Sandoe wrote:
> builtins.def unconditionally defines these builtins to be DEF_EXT_LIB_BUILTIN
> which expands to the libcall, this is currently hard-wired to FALLBACK_P =
> true.
>
> but, AFAIU the builtins.def descriptions:
>
> FALLBACK_P should be false if the libc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104995
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Summary|access checking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108277
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-01-03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107822
--- Comment #2 from Andrew Macleod ---
Sorry, I've been out for a few weeks.
This isn't an on-demand issue. All versions of VRP do a full walk and resolve
during the walk. This issue is a combination of lack of iteration and not
optimistic
LTO compression algorithms: zlib
gcc version 13.0.0 20230103 (experimental) (GCC)
$ gcc/xgcc -B gcc -c ~/toolchain/src/gcc/gcc/testsuite/g++.dg/torture/pr81812.C
-march=armv8-m.main
$ gcc/xgcc -B gcc -c ~/toolchain/src/gcc/gcc/testsuite/g++.dg/torture/pr81812.C
-march=armv8-m.base
/home/alecop01
Hi Richard,
> Hmm, but the point of the original patch was to support code generators
> that emit DW_CFA_val_expression instead of DW_CFA_AARCH64_negate_ra_state.
> Doesn't this patch undo that?
Well it wasn't clear from the code or comments that was supported. I've
added that back in v2.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108276
--- Comment #1 from Andrew Pinski ---
Patches should be sent to gcc-patches@ after reading
https://gcc.gnu.org/contribute.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108206
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108276
Bug ID: 108276
Summary: libiberty unlink_if_ordinary does not handle Windows
nul device correctly
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108275
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
On 2022-12-27 13:25, Jeff Law wrote:
On 12/15/22 12:25, Siddhesh Poyarekar wrote:
Break the _FORTIFY_SOURCE-specific builtins out into a separate
subsection from Object Size Checking built-ins and mention
_FORTIFY_SOURCE in there so that the link between the object size
checking builtins, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108275
Bug ID: 108275
Summary: GCC accepts invalid program using private data member
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60512
Alex Coplan changed:
What|Removed |Added
CC||acoplan at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108237
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108237
--- Comment #4 from Jakub Jelinek ---
Ah, I see, it is forwprop4 which does that:
+Applying pattern match.pd:6223, generic-match.cc:75158
...
- _15 = v.2_7 & { 18446744073709551360, 18446744073709551360 };
- _9 = _15 != { 0, 0 };
+ _9 =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108237
--- Comment #3 from Jakub Jelinek ---
I think the actual problem is though:
/* Transform comparisons of the form (X & Y) CMP 0 to X CMP2 Z
where ~Y + 1 == pow2 and Z = ~Y. */
(for cst (VECTOR_CST INTEGER_CST)
(for cmp (eq ne)
icmp
13.0.0 20230103 (experimental) (GCC)
$ cat t.c
const char *f() { return ""; }
const char *g() { return ""; }
$ gcc/xgcc -B gcc -c t.c -fipa-icf -march=armv8-a -mthumb
during RTL pass: mach
t.c: In function ‘g’:
t.c:2:13: internal compiler error: in df_refs_verify, at df-scan.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108237
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
Florian Weimer changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
--- Comment #2 from Florian Weimer ---
Fixed with the revert in commit 455acc43518744b89d6a795bbba5045bd228060b.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105043
Siddhesh Poyarekar changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105043
--- Comment #9 from CVS Commits ---
The master branch has been updated by Siddhesh Poyarekar
:
https://gcc.gnu.org/g:b3009222b7bb26654c1e93d34e65e8f80ae20595
commit r13-4978-gb3009222b7bb26654c1e93d34e65e8f80ae20595
Author: Siddhesh Poyarekar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108253
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
On Tue, 3 Jan 2023, Jan Hubicka wrote:
> > * gcc/common/config/i386/i386-common.cc (processor_alias_table):
> > Use CPU_ZNVER4 for znver4.
> > * config/i386/i386.md: Add znver4.md.
> > * config/i386/znver4.md: New.
> OK,
> thanks!
Honza, I'm curious what are your further plans
> [Public]
>
> Hello,
>
> I have addressed all your comments in this revision of the patch, please find
> attached and inlined.
>
> * I have updated all the latencies with Agner's measurements.
> * Incorrect pipelines, loads/stores are addressed.
> * The double pumped avx512 insns take one
Ping!
On 2022-12-21 17:25, Siddhesh Poyarekar wrote:
Hi,
The first patch in the series is just a minor test cleanup that I did to
make sure all tests in a test case run (instead of aborting at first
failure) and print the ones that failed. The second patch is the actual
fix.
The patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108269
--- Comment #4 from Camden Mannett ---
> So it is just a minor issue dealing with debugging really ...
__PRETTY_FUNCTION__ is (mis)used for more than that though; it's often used as
an compile-time version of RTTI:
On Tue, Jan 03, 2023 at 02:25:21PM +0100, Florian Weimer wrote:
> > Though, I still wonder, because all of this is a hack for a single target
> > - x86_64-linux -m64 - I think no other target has similar constant
> > sizes,
>
> Really? That's odd.
I've tried about 30 cross compilers I had
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108229
--- Comment #4 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:de59d8bd163a4b2e50ab566441ab49d7212c3356
commit r13-4976-gde59d8bd163a4b2e50ab566441ab49d7212c3356
Author: Roger Sayle
Date: Tue
* Jakub Jelinek:
> On Tue, Jan 03, 2023 at 12:15:23PM +0100, Florian Weimer wrote:
>> --- a/gcc/debug.h
>> +++ b/gcc/debug.h
>> @@ -245,7 +245,18 @@ extern const struct gcc_debug_hooks vmsdbg_debug_hooks;
>>
>> /* Dwarf2 frame information. */
>>
>> -extern int dwarf_reg_sizes_constant ();
This patch is an update/tweak of Andrew Pinski's two patches for
PR tree-optimization/92342, that were originally posted back in November:
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585111.html
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585112.html
Technically, the
On Tue, Jan 03, 2023 at 12:15:23PM +0100, Florian Weimer wrote:
> --- a/gcc/debug.h
> +++ b/gcc/debug.h
> @@ -245,7 +245,18 @@ extern const struct gcc_debug_hooks vmsdbg_debug_hooks;
>
> /* Dwarf2 frame information. */
>
> -extern int dwarf_reg_sizes_constant ();
> +/* Query size information
On Mon, Jan 02, 2023 at 09:20:33AM -0700, Jeff Law wrote:
> On 1/2/23 08:59, Jakub Jelinek wrote:
> >See the PR50161 thread in
> >https://gcc.gnu.org/legacy-ml/gcc-patches/2011-08/threads.html#01847
Nasty nasty nasty.
> >The options are to disallow different modes, which is what my patch did
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106099
Jakub Jelinek changed:
What|Removed |Added
CC||gs...@t-online.de
--- Comment #17 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106257
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
It seems that the default constructor of the non-POD poly-ints does
nothing. Is this intentional? I expected zero initialization, to match
regular ints.
Thanks,
Florian
The previous code had several issues.
1. XALLOCAVEC does not create any objects, so invocating
the non-POD poly_uint16 assignment operator is undefined.
2. The default constructor of poly-ints does not create a
zero poly-int object (unlike what happens with regular ints).
3. The register
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
Jakub Jelinek changed:
What|Removed |Added
Summary|[11/12/13 Regression] ICE |[11/12 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108263
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:226a498733e7919de72eb6f1bf3e16883ad159f6
commit r13-4975-g226a498733e7919de72eb6f1bf3e16883ad159f6
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108263
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4fb639a7fee5df32a2d1e7afa40fdf31d280464b
commit r13-4974-g4fb639a7fee5df32a2d1e7afa40fdf31d280464b
Author: Jakub Jelinek
Date:
Hi Pali,
Hello! I would like to remind this thread for gcc/binutils developers.
Most of these issues are still present and cause problems for compiling
native PE binary. If you have questions or you need any other information
please let me know.
Have bug reports been filed for the individual
> Am 03.01.2023 um 11:34 schrieb Jakub Jelinek via Gcc-patches
> :
>
> Hi!
>
> The following testcase ICEs on s390x-linux (e.g. with -march=z13).
> The problem is that target is (subreg/s/u:SI (reg/v:DI 66 [ x+-4 ]) 4)
> and we call convert_move from temp to the SUBREG_REG of that,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108268
--- Comment #1 from Jakub Jelinek ---
Looking at GCC 12, I think no target actually stored anything into that last
element
unless it was a return or alternate return column.
It is true that expand_builtin_init_dwarf_reg_sizes had:
if
> Am 03.01.2023 um 11:29 schrieb Jakub Jelinek via Gcc-patches
> :
>
> Hi!
>
> The following testcase distilled from Linux kernel on ppc64le ICEs,
> because fixup_reorder_chain sees a bb with a single fallthru edge
> falling into a bb with simple return and decides to redirect
> that
Hi!
The following testcase ICEs on s390x-linux (e.g. with -march=z13).
The problem is that target is (subreg/s/u:SI (reg/v:DI 66 [ x+-4 ]) 4)
and we call convert_move from temp to the SUBREG_REG of that, expecting
to extend the value properly. That works nicely if temp has some
scalar integer
Hi!
The following testcase distilled from Linux kernel on ppc64le ICEs,
because fixup_reorder_chain sees a bb with a single fallthru edge
falling into a bb with simple return and decides to redirect
that fallthru edge to EXIT. That is possible if the bb ending
in the fallthru edge doesn't end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106816
--- Comment #9 from Martin Jambor ---
(In reply to Martin Liška from comment #6)
>
> @Martin: Do we have a declaration cloning code for functions somewhere?
See e.g. cgraph_node::create_virtual_clone in cgraphclones.cc. Unless
you want to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Kewen Lin changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Bug ID: 108273
Summary: Inconsistent dfa state between debug and non-debug
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108256
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Last
From: Ghjuvan Lacambre
Before this commit, when GNAT needed to emit lines longer than
the buffer, it accidentally inserted a newline in its output when
attempting to flush its buffer.
We fix this by using Flush_Buffer instead of Write_Eol in Write_Char.
gcc/ada/
* output.adb
From: Ronan Desplanques
Before this patch, format strings ending with "%%" (two consecutive
percent signs) caused GNAT.Formatted_String."-" to give the wrong
output, and cause the various GNAT.Formatted_String."&" to raise
exceptions with misleading error messages.
Also before this patch, a bug
From: Eric Botcazou
This goes back to the original implementation but keeps the special size
test with universal_integer to cope with its limited range.
gcc/ada/
* sem_res.adb (Resolve_Membership_Op): Adjust again latest change.
Tested on x86_64-pc-linux-gnu, committed on master.
---
From: Ronan Desplanques
Before this patch, passing a width and a precision through
arguments with the "*" syntax always failed for real values in
GNAT.Formatted_String's routines.
gcc/ada/
* libgnat/g-forstr.adb (P_Flt_Format): Add "*" syntax handling.
Tested on x86_64-pc-linux-gnu,
From: Eric Botcazou
The predicate implements the rules of the language so it needs to cope with
constructs rewritten by the expander, in particular explicit dereferences
that the expander uses liberally for various purposes.
This change makes the detection of rewritten calls more robust,
From: Eric Botcazou
Various parts of the expander and the code generator must have a consistent
view on which temporaries generated for return statements must be finalized
because they are regular temporaries, and which ones must not be since they
are allocated on the return stack directly. The
From: Ghjuvan Lacambre
This commit fixes a small bug where GNAT would emit unescaped quotes in
its -fdiagnostics-format=json output when using -gnatdJ and emitting
messages about operator functions (e.g. "=").
gcc/ada/
* errout.adb (Write_JSON_Span): Escape subprogram name.
Tested on
From: Joel Brobecker
The wording of the introduction paragraph specified an incomplete
list of OSes. Rather than trying to update the list, this commit
changes the text to make it more general. For those parts of
this chapter which only apply to specific OSes, the documentation
is written in a
From: Eric Botcazou
Such functions use neither Ada 2005's build-in-place mechanism nor Ada 95's
return-by-reference mechanism, but instead the common calling convention of
functions returning a nonlimited by-reference type.
gcc/ada/
* exp_ch6.adb (Is_Build_In_Place_Function): Adjust
From: Eric Botcazou
The predicate implements the rules of the language so it needs to cope with
constructs rewritten by the expander, in particular explicit dereferences
that the expander uses liberally for various purposes.
This change makes the detection of rewritten calls more robust and
1 - 100 of 117 matches
Mail list logo
