Hi,
in Fortran, it would sometimes be useful to have a different optimization
depending on whether we generate inlined code for intrinsics (where we
know when it is OK to „go wild“) or user code, where we need to
adhere (for example) to IEEE semantics unless otherwise instructed
by the user.
Wh
Hello Everyone,
Consider the following test case:
[..]
int main () {
__int128 newVar = 8;
newVar = ~newVar;
return 0;
}
[..]
Compiled as: $gcc foo.c -g -O1
produces DWARF for "newVar" as:
[..]
0x004f: DW_TAG_variable
DW_AT_name("newVar")
On Sat, Jul 04, 2020 at 04:23:58PM +, Tomar, Sourabh Singh wrote:
> Consider the following test case:
> [..]
> int main () {
> __int128 newVar = 8;
> newVar = ~newVar;
> return 0;
> }
DW_OP_implicit_value as well as DW_OP_stack_value is described in DWARF4/5,
just read
On July 4, 2020 11:30:05 AM GMT+02:00, "Thomas König" wrote:
>Hi,
>
>in Fortran, it would sometimes be useful to have a different
>optimization
>depending on whether we generate inlined code for intrinsics (where we
>know when it is OK to „go wild“) or user code, where we need to
>adhere (for ex
Snapshot gcc-10-20200704 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20200704/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
