public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>, gcc-patches@gcc.gnu.org
Cc: Eugene Rozenfeld <erozen@microsoft.com>
Subject: Re: [PATCH] skip debug stmts when assigning locus discriminators
Date: Wed, 8 Nov 2023 14:28:14 -0700	[thread overview]
Message-ID: <ed589cd1-ea73-42dd-bffe-546af3102f47@gmail.com> (raw)
In-Reply-To: <or1qd0jlac.fsf@lxoliva.fsfla.org>



On 11/8/23 08:51, Alexandre Oliva wrote:
> 
> c-c++-common/goacc/kernels-loop-g.c has been failing (compare-debug)
> on i686-linux-gnu since r13-3172, because the implementation enabled
> debug stmts to cause discriminators to be assigned differently, and
> the discriminators are printed in the .gkd dumps that -fcompare-debug
> compares.
> 
> This patch prevents debug stmts from affecting the discriminators in
> nondebug stmts, but enables debug stmts to get discriminators just as
> nondebug stmts would if their line numbers match.
> 
> I suppose we could arrange for discriminators to be omitted from the
> -fcompare-debug dumps, but keeping discriminators in sync is probably
> good to avoid other potential sources of divergence between debug and
> nondebug.
> 
> Regstrapped on x86_64-linux-gnu, also tested with gcc-13 on i686- and
> x86_64-.  Ok to install?
> 
> (Eugene, I suppose what's special about this testcase, that may not
> apply to most other uses of assign_discriminators, is that goacc creates
> new functions out of already optimized code.  I think
> assign_discriminators may not be suitable for new functions, with code
> that isn't exactly pristinely in-order.  WDYT?)
> 
> 
> for  gcc/ChangeLog
> 
> 	* tree-cfg.cc (assign_discriminators): Handle debug stmts.
OK
jeff

  reply	other threads:[~2023-11-08 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 15:51 Alexandre Oliva
2023-11-08 21:28 ` Jeff Law [this message]
2023-11-09  2:46 ` [EXTERNAL] " Eugene Rozenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed589cd1-ea73-42dd-bffe-546af3102f47@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=erozen@microsoft.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=oliva@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).