public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105355] -msmall-data-limit= unexpectedly accepts a separate argument Date: Tue, 26 Apr 2022 09:31:19 +0000 [thread overview] Message-ID: <bug-105355-4-Z2ulX8Ao1S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105355-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105355 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org Last reconfirmed| |2022-04-26 CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- I think it's bogus having Separate and Joined properties for an option that ends with '='. We've got one more example and it leads to bogus: $ gcc -output-pch= pes.pch a.c --save-temps --verbose ... /home/marxin/bin/gcc/libexec/gcc/x86_64-pc-linux-gnu/12.0.1/cc1 -fpreprocessed utput-pch=-a.i ... which is wrongly truncated. I'm going to fix it.
next prev parent reply other threads:[~2022-04-26 9:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-22 23:20 [Bug driver/105355] New: " izbyshev at ispras dot ru 2022-04-26 9:31 ` marxin at gcc dot gnu.org [this message] 2022-04-26 9:35 ` [Bug target/105355] " marxin at gcc dot gnu.org 2022-04-26 9:39 ` marxin at gcc dot gnu.org 2022-04-26 10:06 ` izbyshev at ispras dot ru 2022-05-11 6:56 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:57 ` marxin at gcc dot gnu.org 2022-05-11 15:46 ` palmer 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-105355-4-Z2ulX8Ao1S@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).