> Do you know someone very familiar with MIPS and GCC and capable as a
> port maintainer? An active MIPS port maintainer will make the situation
> better.
Sadly, no. I agree it would make things easier.
From: Xi Ruoyao
Sent: Wednesday, July 27, 2022 8:43 AM
To: Dimitrije Milosevic ;
gcc-patche
On Wed, 27 Jul 2022, juzhe.zh...@rivai.ai wrote:
> From: zhongjuzhe
>
> gcc/ChangeLog:
>
> * expr.cc (expand_assignment): Change GET_MODE_PRECISION to
> GET_MODE_BITSIZE
>
> ---
> gcc/expr.cc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/expr.cc b/gcc/
On Wed, 2022-07-27 at 06:41 +, Dimitrije Milosevic wrote:
> Gentle ping, requiring someone to push this change, as I do not have
> commit access. :)
Do you know someone very familiar with MIPS and GCC and capable as a
port maintainer? An active MIPS port maintainer will make the situation
bet
Gentle ping, requiring someone to push this change, as I do not have commit
access. :)
From: Dimitrije Milosevic
Sent: Monday, July 25, 2022 8:55 AM
To: gcc-patches@gcc.gnu.org
Cc: Djordje Todorovic ; xry...@xry111.site
Subject: [PATCH] libsanitizer: Cherry-pick 2bfb0fcb51510f22723c8cdfefe fro
On Tue, 26 Jul 2022, Marek Polacek wrote:
> Since r11-5188-g32934a4f45a721, we drop qualifiers during l-to-r
> conversion by creating a NOP_EXPR. For e.g.
>
> const int i = i;
>
> that means that the DECL_INITIAL is '(int) i' and not 'i' anymore.
> Consequently, we don't suppress_warning here
On Jul 11, 2022, Mike Stump wrote:
> On Jul 11, 2022, at 6:47 PM, Alexandre Oliva wrote:
>>
>> Running the testsuite on a toolchain build with --enable-default-pie
>> had some unexpected fails.
>> Regstrapped on x86_64-linux-gnu, and also tested on i686-linux-gnu, with
>> and without --enable-
g++.dg/ext/attr-ifunc-3.C and gcc.target/i386/mvc10.c, not changed,
have made it clear that there were problems in the optimizations to
use @GOTOFF to refer to locally-bound ifuncs. GNU ld as recently as
May 2018 would reject such constructs, whereas later versions will
silently accept but gener
Looking at the code generated for sse2-{load,store}-multi.c with PIE,
I realized we could use UNSPEC_GOTOFF as a base address, and that this
would enable the test to use the vector insns expected by the tests
even with PIC, so I extended the base + offset logic used by the SSE2
multi-load/store p
From: zhongjuzhe
Hi, variable "bitpos" is compute using bitsize. I think it makes
sense for bit position checking whether it is out-of-bounds to
array using GET_MODE_BITSIZE instead of GET_MODE_PRECISION.
This patch is useful for RVV (RISC-V 'V') support that I am
going to push upstream. Thanks!
From: zhongjuzhe
gcc/ChangeLog:
* expr.cc (expand_assignment): Change GET_MODE_PRECISION to
GET_MODE_BITSIZE
---
gcc/expr.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/expr.cc b/gcc/expr.cc
index 80bb1b8a4c5..ac2b3c07df6 100644
--- a/gcc/expr.cc
+++ b/gcc/
On Wed, 2022-07-27 at 09:34 +0800, Lulu Cheng wrote:
> > -- >8 --
> >
> > The assembly produced with -mexplicit-relocs is not supported by gas
> > <=
> > 2.39. Check if the assembler supports explicit relocations and set
> > the
> > default accordingly.
> Looks good to me.
Pushed r13-1851.
在 2022/7/26 下午10:15, Xi Ruoyao 写道:
The following should work. I've tested it locally by building GCC with
both old (2.38 with patch) and new (trunk) Binutils. Ok for trunk?
I simply checked as instead of ld. If as supports explicitly
relocations, the produced .o file won't be supported by a
This is now committed to trunk, backported to releases/gcc-12 and
releases/gcc-11.
Apologies for the delay, it's been a wild couple of weeks.
Tom.
On Thu, Jul 7, 2022 at 2:31 AM Jonathan Wakely wrote:
> On Wed, 6 Jul 2022 at 22:42, Thomas Rodgers wrote:
> >
> > Ok for trunk? backport?
>
> Yes
Hi!
On Tue, Jul 26, 2022 at 10:04:45PM +0100, Roger Sayle wrote:
> It's very important to distinguish the invariants that exist for the RTL
> data structures as held in memory (rtx),
"In memory"? What does that mean here? RTX are just RTL expressions,
nothing more, nothing less.
> vs. the use
On 7/22/22 4:23 AM, Jose E. Marchesi via Gcc-patches wrote:
Contrary to CTF and our previous expectations, as per [1], turns out
that in BTF:
1) The `encoding' field in integer types shall not be treated as a
bitmap, but as an enumerated, i.e. these bits are exclusive to each
other.
2)
Hi,
This patch merges the D front-end with upstream dmd 76e3b41375, and
standard run-time libraries with druntime 1462ebd1, and phobos
5fef0d28f, updating the D language version to v2.100.1.
D front-end changes:
- Fix delegate literal with inferred return value that requires
following
On Thu, 7 Jul 2022, Kito Cheng wrote:
> +/* Implement TARGET_MANGLE_TYPE. */
> +
> +static const char *
> +riscv_mangle_type (const_tree type)
> +{
> + /* Half-precision float. */
> + if (TREE_CODE (type) == REAL_TYPE && TYPE_PRECISION (type) == 16)
> +return "Dh";
Are you sure you wish t
Hi!
On Tue, Jul 19, 2022 at 10:30:54PM +0800, Jiufu Guo wrote:
> In patch https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597712.html,
> test case was not added. After more check, a testcase is added for it.
>
> The high part of the symbol address is invalid for the constant pool.
Invalid,
On Tue, Jul 26, 2022 at 04:24:18PM -0400, Jason Merrill wrote:
> On 7/26/22 15:03, Marek Polacek wrote:
> > Since r11-5188-g32934a4f45a721, we drop qualifiers during l-to-r
> > conversion by creating a NOP_EXPR. For e.g.
> >
> >const int i = i;
> >
> > that means that the DECL_INITIAL is '(i
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-1848-gdb613e8fa84125.
gcc/analyzer/ChangeLog:
PR analyzer/106319
* store.cc (store::set_value): Don't strip away casts if the
region has NULL type.
gcc/testsuite/ChangeLog:
PR ana
Hi Segher,
It's very important to distinguish the invariants that exist for the RTL
data structures as held in memory (rtx), vs. the use of "enum rtx_code"s,
"machine_mode"s and operands in the various processing functions
of the middle-end.
Yes, it's very true that RTL integer constants don't s
On 7/26/22 15:03, Marek Polacek wrote:
Since r11-5188-g32934a4f45a721, we drop qualifiers during l-to-r
conversion by creating a NOP_EXPR. For e.g.
const int i = i;
that means that the DECL_INITIAL is '(int) i' and not 'i' anymore.
Consequently, we don't suppress_warning here:
711 case
Le 25/07/2022 à 22:18, Harald Anlauf a écrit :
I would normally trust NAG more than Intel and Cray.
… and yourself, it seems. Too bad.
If somebody else convinces me to accept that NAG has it wrong this time, I
would be happy to proceed.
It won’t convince you about NAG, but here are two rea
Since r11-5188-g32934a4f45a721, we drop qualifiers during l-to-r
conversion by creating a NOP_EXPR. For e.g.
const int i = i;
that means that the DECL_INITIAL is '(int) i' and not 'i' anymore.
Consequently, we don't suppress_warning here:
711 case DECL_EXPR:
715 if (VAR_P (DECL_EXPR
These were copy&paste errors.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-1847-g0460ba622e833d.
gcc/analyzer/ChangeLog:
* region.h (code_region::get_element): Remove stray decl.
(function_region::get_element): Likewise.
Signed-off-by: Dav
Standardize the formatting of SFB ALU conditional move operations from:
beq a2,zero,1f; mv a0,zero; 1: # movcc
to:
beq a2,zero,1f # movcc
mv a0,zero
1:
for consistency with other assembly code produced. No functional change.
gcc/
* gcc/con
Hi!
On Tue, Jul 26, 2022 at 01:13:02PM +0100, Roger Sayle wrote:
> This patch is a major revision of the patch I originally proposed here:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598040.html
>
> The primary motivation of this patch is to avoid incorrect optimization
> of MODE_CC com
Hi Maciej:
Ooops, thanks for fixing that, the change was gotten from kernel
folks. I assume they have already used that for a while, but it's
really weird no bug report from those guys...
OK for trunk and backport for release branch.
On Wed, Jul 27, 2022 at 1:00 AM Maciej W. Rozycki wrote:
>
>
Remove redundant duplicate backslash characters from \t sequences in the
output pattern of the `stack_protect_set_' RTL insn.
gcc/
* gcc/config/riscv/riscv.md (stack_protect_set_): Remove
duplicate backslashes.
---
Hi,
I don't know why it doesn't matter whether the back
On Tue, 2022-07-26 at 22:07 +0530, Immad Mir wrote:
> This patch adds get_meaning_for_state_change vfunc to
> fd_diagnostic in sm-fd.cc which could be used by SARIF output.
>
> Lightly tested on x86_64 Linux.
Thanks - looks good for trunk.
Dave
This patch adds get_meaning_for_state_change vfunc to
fd_diagnostic in sm-fd.cc which could be used by SARIF output.
Lightly tested on x86_64 Linux.
gcc/analyzer/ChangeLog:
PR analyzer/106286
* sm-fd.cc:
(fd_diagnostic::get_meaning_for_state_change): New.
gcc/testsuite/Ch
Firstly many thanks again to Jeff Law for reviewing/approving the previous
patch to add support for ABIs that pass FP values as wider integer modes.
That has allowed significant progress on PR target/104489. As predicted
enabling HFmode on nvptx-none automatically enables more testcases in the
te
On Tue, 2022-07-26 at 06:55 +0200, Martin Liška wrote:
> gcc/jit/ChangeLog:
>
> * docs/index.rst: Remove reference to module index
> as we don't emit any.
Patch is OK
Thanks
Dave
> ---
> gcc/jit/docs/index.rst | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/gcc/jit/doc
On Tue, 2022-07-26 at 06:50 +0200, Martin Liška wrote:
> On 7/26/22 00:41, David Malcolm wrote:
> > On Mon, 2022-07-25 at 14:39 +0200, Martin Liska wrote:
> > > gcc/jit/ChangeLog:
> > >
> > > * docs/cp/intro/tutorial02.rst: Use :expr:`type *` for
> > > pointers to a type
> > > * do
On Tue, 2022-07-26 at 06:48 +0200, Martin Liška wrote:
> On 7/26/22 00:37, David Malcolm wrote:
> > On Mon, 2022-07-25 at 11:03 +0200, Martin Liska wrote:
> > > Use expression that work fine for basic type.
> >
> > What's the motivation for this change? Surely the things being
> > marked
> > up a
On Tue, 2022-07-26 at 08:42 +0200, Martin Liška wrote:
> Shorten the assembly example so that there is not slider.
>
> Ready for master?
OK, thanks
Dave
On 7/26/22 1:57 AM, Richard Biener via Gcc-patches wrote:
>> On 6/17/22 11:50 PM, Peter Bergner via Gcc-patches wrote:
>>> The initial commit that added opaque types thought that there couldn't
>>> be any valid initializations for variables of these types, but the test
>>> case in the bug report sh
>
> int f(_Complex int x, _Complex int y)
> {
> return x == x / y * y;
> }
>
After some research about mod with complex types, I found that the binary
mod operation does not work with complex types. If so, the complex test
case should not be simplified. Is this correct?
I should also note that
> > Maybe we can add a check in gcc/configure.ac to see if gcc_cv_ld
> > supports %got_pc_hi20 and adjust the default for -m[no]-explicit-relocs?
> I think this is a good way, I'll look at adding a check.
The following should work. I've tested it locally by building GCC with
both old (2.38 with
The following adds a pattern for ifcombine to match an address overlap
check and use alias analysis to decide overlap at compile-time. This
happens with code generated from std::string as shown in the PR even
if meanwhile the trunk generated code causes the pattern to no longer
match.
Bootstrappe
The following improves on the fix for PR105142 which restricted the
expression lookup used for maybe_fold_comparisons_from_match_pd to
avoid picking up flow-sensitive info for use in places where guarding
conditions do not hold. Instead of not allowing to expand SSA
definitions there the following
在 2022/7/26 下午8:01, Xi Ruoyao 写道:
On Tue, 2022-07-26 at 19:42 +0800, Lulu Cheng wrote:
在 2022/7/26 下午5:44, Xi Ruoyao 写道:
+ whether the la.* macro instructions will be generated when
+ loading symbolic addresses.
+ This feature requires binutils version 2.40 or later. If you want to use th
在 2022/7/26 下午7:32, Gerald Pfeifer 写道:
On Tue, 26 Jul 2022, Lulu Cheng wrote:
+LoongArch
+
+ The option -mexplicit-relocs has been added, this indicates
+ whether the la.* macro instructions will be generated when
+ loading symbolic addresses.
How about making this "...has been added. It i
On 7/26/22 14:01, Jonathan Wakely via Gcc-patches wrote:
> On Tue, 26 Jul 2022 at 12:56, Frank Ch. Eigler wrote:
>>
>> Hi -
>>
The gccadmin team can do this kind of thing without overseer/root
privileges, or indeed so can any local shell-privileged user.
>>>
>>> Yeah, I said I didn't want
This patch is a major revision of the patch I originally proposed here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598040.html
The primary motivation of this patch is to avoid incorrect optimization
of MODE_CC comparisons in simplify_const_relational_operation when/if a
backend represent
On Tue, 26 Jul 2022 at 12:56, Frank Ch. Eigler wrote:
>
> Hi -
>
> > > The gccadmin team can do this kind of thing without overseer/root
> > > privileges, or indeed so can any local shell-privileged user.
> >
> > Yeah, I said I didn't want to install it that way without overseer
> > approval, as pi
On Tue, 2022-07-26 at 19:42 +0800, Lulu Cheng wrote:
> 在 2022/7/26 下午5:44, Xi Ruoyao 写道:
> >
> > > + whether the la.* macro instructions will be generated when
> > > + loading symbolic addresses.
> > > + This feature requires binutils version 2.40 or later. If you want to
> > > use the
> > >
Hi -
> > The gccadmin team can do this kind of thing without overseer/root
> > privileges, or indeed so can any local shell-privileged user.
>
> Yeah, I said I didn't want to install it that way without overseer
> approval, as pip won't keep the packages up to date the way dnf
> installations do.
On Tue, 26 Jul 2022 at 12:45, Frank Ch. Eigler wrote:
>
> Hi -
>
> > CCing overseers and Frank.
> > Can you please help me with that?
>
> > > Can please a maintainer install the package from pip?
> > > Something like:
> > > virtualenv /home/gcc/venv && /home/gcc/venv/bin/pip install Sphinx
> > > o
Hi -
> CCing overseers and Frank.
> Can you please help me with that?
> > Can please a maintainer install the package from pip?
> > Something like:
> > virtualenv /home/gcc/venv && /home/gcc/venv/bin/pip install Sphinx
> > or a similar location?
The gccadmin team can do this kind of thing withou
在 2022/7/26 下午5:44, Xi Ruoyao 写道:
+ whether the la.* macro instructions will be generated when
+ loading symbolic addresses.
+ This feature requires binutils version 2.40 or later. If you want to use the
+ older version of bintuils, add compiler parameters
+ -mno-explicit-relocs at compi
On Tue, 26 Jul 2022, Lulu Cheng wrote:
> +LoongArch
> +
> + The option -mexplicit-relocs has been added, this
> indicates
> + whether the la.* macro instructions will be generated when
> + loading symbolic addresses.
How about making this "...has been added. It indicates..." or, if you
prefer
The following improves on the fix for PR105142 which restricted the
expression lookup used for maybe_fold_comparisons_from_match_pd to
avoid picking up flow-sensitive info for use in places where guarding
conditions do not hold. Instead of not allowing to expand SSA
definitions there the following
Technically iranges only exist in constant form, but we allow symbolic
ones before arriving in the ranger, so legacy VRP can work. This fixes the
ICE when attempting to print symbolic iranges in the pretty printer.
For consistency's sake, I have made sure irange::get_nonzero_bits does
not similar
When the first pointer happens to be a pointer to a STRING_CST we
give up too early since the 2nd pointer handling could still end
up with a DECL for example which can disambiguate against a STRING_CST
just fine.
Boostrapped and tested on x86_64-unknown-linux-gnu, pushed.
* tree-ssa-alias
Hi,
This is a RFC for my prototype for bitfield read vectorization. This
patch enables bit-field read vectorization by removing the rejection of
bit-field read's during DR analysis and by adding two vect patterns. The
first one transforms TREE_COMPONENT's with BIT_FIELD_DECL's into
BIT_FIELD_
+Xuerui (his English is much better than mine).
On Tue, 2022-07-26 at 15:21 +0800, Lulu Cheng wrote:
> Hi,
> Recently we added split symbol support, changed in r13-1834.
> It is ok for wwwdocs?
> +LoongArch
> +
> + The option -mexplicit-relocs has been added, this indicate
I think "added an
Hi Gaius,
> Rainer Orth writes:
>
>>> I think this just leaves:
>>>
* While this lets the build finish on all of i386-pc-solaris2.11,
sparcv9-sun-solaris2.11, and x86_64-pc-linux-gnu, I get thousands of
testsuite failures, all of the same kind:
Undefined
CCing overseers and Frank.
Can you please help me with that?
Thanks,
Martin
On 7/25/22 16:00, Martin Liška wrote:
> Hi.
>
> As you likely know, I'm still working on transition of the current docs to
> Sphinx.
> But for now, I've sent a modernizing patches for the current libgccjit
> documenta
Hi,
Recently we added split symbol support, changed in r13-1834.
It is ok for wwwdocs?
Thanks!
Lulu Cheng
---
htdocs/gcc-13/changes.html | 21 +
1 file changed, 21 insertions(+)
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 57bd8724..60399e4e
Le 25/07/2022 à 22:39, Harald Anlauf via Fortran a écrit :
Dear all,
we currently may ICE when array bounds of a dummy argument have
a non-integer type, and the procedure with the bad declaration is
referenced. The same applies to bad character length of dummies.
We could simply punt in such a
61 matches
Mail list logo
