On 8/13/24 10:16 PM, Li, Pan2 wrote:
How specifically is it avoided for SI? ISTM it should have the exact
same problem with a constant like 0x8000 in SImode on rv64 which is
going to be extended to 0x8000.
HI and QI need some special handling for sum. For example, for HImode
On Thu, Aug 15, 2024 at 9:23 PM Jeff Law wrote:
>
>
>
> On 8/13/24 10:16 PM, Li, Pan2 wrote:
> >> How specifically is it avoided for SI? ISTM it should have the exact
> >> same problem with a constant like 0x8000 in SImode on rv64 which is
> >> going to be extended to 0x8000.
> >
On 8/7/24 1:25 AM, Manolis Tsamis wrote:
On Wed, Aug 7, 2024 at 8:57 AM Sam James wrote:
Philipp Tomsich writes:
Hi,
Sam, Jakub & Robin,
We had an "OK for trunk" from Jeff for v4 (see
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/656907.html) and
it has been two more weeks for th
Hi Harald,
s/doumentation/documentation/
in the commit's title.
Thanks for the patch, ok to commit.
- Andre
On Thu, 15 Aug 2024 22:37:53 +0200
Harald Anlauf wrote:
> Dear all,
>
> here's a documentation bugfix. The previous wording was in conflict
> with the standard, while the runtime beha
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
When reading an NTTP we call get_template_parm_object which delegates
setting of DECL_INITIAL to the general cp_finish_decl procedure, which
calls check_initializer to validate and record it.
Apart from being unnecessary (
101 - 105 of 105 matches
Mail list logo