> Ohh, my fault: the `-flto` option should always be skipped, when run test.
Right, if tests run with `-flto` option, they will fail. However, I do believe
they are run only if LTO support is enabled, that's why my tests all passed
without explicitly skipping that option.
Your modification looks
necessary, so I've removed that part.
I've fixed the Changelog, hopefully I've corrected the mistakes I made.
Regards,
JovanFrom 05e4ff4d2fbb91ea8040fb10d8d6a130ad24bba7 Mon Sep 17 00:00:00 2001
From: Jovan Dmitrovic
Date: Mon, 26 Jun 2023 17:00:20 +0200
Subject: [PATCH] mips:
I see what you mean now, so I've made adjustment in order for testcase to work
on assembly. Following is the updated patch.
Regards,
Jovan
>From 2744357b5232c61bf1f780c4915d47b19d71f993 Mon Sep 17 00:00:00 2001
From: Jovan Dmitrovic
Date: Fri, 19 May 2023 12:36:55 +0200
Subject: [PAT
whether
writing this testcase as an assembly check would make sense,
because that would make the testcase much less readable.
From: YunQiang Su
Sent: Wednesday, May 31, 2023 12:05 PM
To: Jovan Dmitrovic
Cc: gcc-patches@gcc.gnu.org; Djordje Todorovic
Subject: Re: [PATCH] mips
This patch changes alignment for typedef types when passed as
arguments, making the alignment equal to the alignment of
original (aliased) types.
This change makes it impossible for a typedef type to have
alignment that is less than its size.
Signed-off-by: Jovan Dmitrovic
gcc/ChangeLog
Hi Richard,
I had pinged the community about this problem back in March, and I will be
taking Dimitrije's place, considering he isn't working on these patches anymore.
Your solution for 2/2 seems reasonable, I don't exactly know why
target_reg_cost hasn't been accounted for in the first case, no
Ping for patch from December 2022:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608896.html
Ping for patch from December 2022:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608895.html
