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 testsuite/95577] Tcl error with testsuite/gcc.misc-tests/outputs.exp on darwin Date: Wed, 24 Jun 2020 20:24:06 +0000 [thread overview] Message-ID: <bug-95577-4-dFyZqLEGx2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95577-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95577 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:ef6506e23691a72e1e724977e8ee8b9f3db74015 commit r11-1642-gef6506e23691a72e1e724977e8ee8b9f3db74015 Author: Alexandre Oliva <oliva@adacore.com> Date: Wed Jun 24 17:20:49 2020 -0300 outputs.exp: conditionals for split-dwarf and lto plugin This patch introduces support for conditionals (and expr) expansions to file lists in proc outest in outputs.exp. The conditionals machinery is now used to guard files that are only created by the LTO plugin, or when not using the LTO plugin. It is also used to avoid special-casing .dwo files: the condition of when they're expected is now encoded in the list. Furthermore, the -g flag, that used to be specified along with $gsplit_dwarf, is now moved into $gsplit_dwarf, so that we don't compile with -g if -gsplit-dwarf is not needed. This avoids having to deal with .dSYM directories. Further removing special cases, $aout is now dealt with in a more general way, using expr to perform variable/string expansion. for gcc/testsuite/ChangeLog PR testsuite/95416 PR testsuite/95577 * gcc.misc-tests/outputs.exp (gsplit_dwarf): Move -g into it. (outest): Introduce conditionals and string/variable/expr expansion. Drop special-casing of $aout and .dwo. (gspd): New conditional. Guard all .dwo files with it. (ltop): New conditional. Guard files created by the LTO plugin with it. Guard files created by fat LTO compilation with its negation. Add a few -fno-use-linker-plugin tests guarded by it.
next prev parent reply other threads:[~2020-06-24 20:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 14:24 [Bug testsuite/95577] New: " dominiq at lps dot ens.fr 2020-06-08 15:06 ` [Bug testsuite/95577] " iains at gcc dot gnu.org 2020-06-09 7:36 ` iains at gcc dot gnu.org 2020-06-23 11:17 ` aoliva at gcc dot gnu.org 2020-06-23 11:45 ` iains at gcc dot gnu.org 2020-06-23 13:16 ` aoliva at gcc dot gnu.org 2020-06-23 13:31 ` iains at gcc dot gnu.org 2020-06-23 13:58 ` aoliva at gcc dot gnu.org 2020-06-23 16:42 ` dominiq at lps dot ens.fr 2020-06-24 20:24 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-24 20:41 ` aoliva 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-95577-4-dFyZqLEGx2@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).