Iain Sandoe via Gcc wrote:
Jakub Jelinek via Gcc wrote:
On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote:
Darwin: Darwin 20 is to be macOS 11 (Big Sur).
So, I'm afraid it must fail or bypass this code path somewhere earlier
in the hooks.
Is that maybe already known to the r
Hi,
I implemented simple propagation of EAF arguments for ipa-modref (that is not
hard to do). My main aim was to detect cases where THIS parameter does not
escape but is used to read/write pointed to memory. This is meant to
avoid poor code produced when we i.e. offline destructors on cold path.
Snapshot gcc-11-20201108 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20201108/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
The current development docs say:
>x86-64-v2
>x86-64-v3
>x86-64-v4
>
> These choices for cpu-type select the corresponding
> micro-architecture level from the x86-64 psABI. They are only available
> when compiling for an x86-64 target that uses the System V psABI.
>
> Since these cpu-type va
I’m woking on TARGET_PROMOTE_FUNCTION_MODE for csky, and now there’s some
confusion.
For csky, the “POMOTE_MODE” is:
qi/hi -> si
the code is
#define PROMOTE_MODE(MODE, UNSIGNEDP, TYPE) \
if (GET_MODE_CLASS (MODE) == MODE_INT \
&& GET_MODE_SIZE (MODE) < UNITS_PER_WORD) \
(MO
On Sun, 8 Nov 2020, Jan Hubicka wrote:
> Hi,
> I implemented simple propagation of EAF arguments for ipa-modref (that is not
> hard to do). My main aim was to detect cases where THIS parameter does not
> escape but is used to read/write pointed to memory. This is meant to
> avoid poor code produ
On 11/6/20 8:59 PM, Jakub Jelinek wrote:
I think I'll work with Martin early next week to think about further spots
to add logging, so we narrow down where it is still called and where it
isn't.
Hello.
I'm suggesting to use the following extra logging.
Martin
>From a39631f6515b60ae2a3c8de0129
