[Bug middle-end/86698] Misleading dump-file contents

[Bug middle-end/86698] Misleading dump-file contents

[erozen at microsoft dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86698

Eugene Rozenfeld <erozen at microsoft dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erozen at microsoft dot com

--- Comment #2 from Eugene Rozenfeld <erozen at microsoft dot com> ---
Currently (as of commit 5700973f4a30762b4fc21687bb5f7843e55da2e4) the dump
looks like this for this function:

;; Function int f(int, int) (null)
;; enabled by -tree-original


{
  int x;

    int x;
  <<cleanup_point <<< Unknown tree: expr_stmt
  (void) (x = (void) z++ ;, y) >>>>>;
  return <retval> = x;
}

This is different from before but there is a duplicate declaration of x, the
semicolon before the colon could be removed, and Unknown tree annotation is not
helpful.

[Bug middle-end/86698] Misleading dump-file contents

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86698

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |23872

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Eugene Rozenfeld from comment #2)
> Currently (as of commit 5700973f4a30762b4fc21687bb5f7843e55da2e4) the dump
> looks like this for this function:

That is from the C++ front-end rather than the C front-end.

(In reply to Richard Earnshaw from comment #0)
> Firstly, the statement is printed twice, which seems to imply that the side
> effects are performed twice. 

That part of the problem is recorded as PR 23872; I will be working on a patch
for GCC 15.

The semi-colon I have not looked into yet though.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23872
[Bug 23872] .original dump weirdness

[Bug middle-end/86698] Misleading .original (generic) dump-file contents

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86698

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The semicolon comes from print_declaration So this is just a dup of bug 23872
in the end.

*** This bug has been marked as a duplicate of bug 23872 ***

[Bug middle-end/86698] Misleading .original (generic) dump-file contents

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86698

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> The semicolon comes from print_declaration So this is just a dup of bug
> 23872 in the end.
> 
> *** This bug has been marked as a duplicate of bug 23872 ***

Actually the semicolon didn't come from there but from COMPOUND_EXPR (but
anyways I am fixing both).