public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102766] [12 Regression][nvptx] internal compiler error: in df_insn_delete, at df-scan.c:949 Date: Thu, 21 Oct 2021 13:20:49 +0000 [thread overview] Message-ID: <bug-102766-4-edEhCzdQJJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102766-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102766 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:b4702276615ff8d43bc910e7a54fdd850ad8d461 commit r12-4608-gb4702276615ff8d43bc910e7a54fdd850ad8d461 Author: Martin Liska <mliska@suse.cz> Date: Thu Oct 14 14:57:18 2021 +0200 options: Fix variable tracking option processing. PR debug/102585 PR bootstrap/102766 gcc/ChangeLog: * opts.c (finish_options): Process flag_var_tracking* options here as they can be adjusted by optimize attribute. Process also flag_syntax_only and flag_gtoggle. * toplev.c (process_options): Remove it here. * common.opt: Make debug_nonbind_markers_p as PerFunction attribute as it depends on optimization level. gcc/testsuite/ChangeLog: * gcc.dg/pr102585.c: New test.
next prev parent reply other threads:[~2021-10-21 13:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 8:31 [Bug bootstrap/102766] New: [12 Regression] " burnus at gcc dot gnu.org 2021-10-15 9:17 ` [Bug bootstrap/102766] [12 Regression][nvptx] " burnus at gcc dot gnu.org 2021-10-15 9:22 ` marxin at gcc dot gnu.org 2021-10-15 9:39 ` burnus at gcc dot gnu.org 2021-10-15 9:45 ` marxin at gcc dot gnu.org 2021-10-15 10:32 ` marxin at gcc dot gnu.org 2021-10-15 10:43 ` burnus at gcc dot gnu.org 2021-10-21 12:31 ` [Bug middle-end/102766] " burnus at gcc dot gnu.org 2021-10-21 13:20 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-21 13:21 ` marxin at gcc dot gnu.org
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=bug-102766-4-edEhCzdQJJ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).