The manual says that the first argument of a TARGET_MEM_REF
"is @code{TMR_SYMBOL} and must be a @code{VAR_DECL} of an object
with a fixed address."
The TARGET_MEM_REF below has as its first argument an ADDR_EXPR
and not a VAR_DECL as the manual claims. The code I looked at
seems to be prepa
Martin Sebor writes:
> Can this option be used in attribute optimize? If yes, what's
> the advantage of also providing an atttribute?
Compatibility with the clang attribute.
> It seems to me that as a matter of QOI, GCC should be able to
> disable the expansion of built-ins to calls to themsel
On 11/2/21 3:14 PM, Keith Packard via Gcc-patches wrote:
This attribute controls optimizations which make assumptions about the
semantics of builtin functions. Typical cases here are code which
match memcpy, calloc, sincos, or which call builtins like free.
This extends on things like the -ftree
Hi all,
There is an agenda for tomorrow's meeting. If you have topics to
discuss or share, please let me know and I can add them to the agenda.
Agenda:
1. Progress of RISC-V sub-extension supports
2. Open Discussion
Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
Topic: RISC-V G
