public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/102343] gm2/cpp/pass/subaddr.mod FAILs for non-default multilib Date: Tue, 17 Jan 2023 16:52:20 +0000 [thread overview] Message-ID: <bug-102343-4-eNMjvW4VcF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102343-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102343 --- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> --- Created attachment 54289 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54289&action=edit Patch for discussion This applies on top of the patch for PR108182 (and will most likely not work without those changes). * -save-temps* should be fixed * we no longer try to write those files into the install directories * we should now support " gm2 -E .... " * renamed the pre-processed file extension to ".m2i" we cannot use ".i" or GCC will try to process it with cc1. * We now have default handers for .mod and .m2i (maybe we should add .def is that something used stand-alone?) So trying to use them with a compiler without modula-2 should give a more sensible diagnostic. * we should handle " gm2 foo.mod.m2i " * last, but most important, we now collect the command line options needed to set the target state into the preprocessor command line. This then provides the correct pre-defines and the test case then does the right thing on a 32b multilib on a 64b host. If there are no comments in the next week or so I'll post this to the list.
next prev parent reply other threads:[~2023-01-17 16:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 11:15 [Bug modula2/102343] New: " ro at gcc dot gnu.org 2023-01-17 15:18 ` [Bug modula2/102343] " iains at gcc dot gnu.org 2023-01-17 16:52 ` iains at gcc dot gnu.org [this message] 2023-01-22 0:22 ` iains at gcc dot gnu.org 2023-01-25 15:24 ` cvs-commit at gcc dot gnu.org 2023-01-25 15:45 ` iains at gcc dot gnu.org 2023-01-27 8:48 ` cvs-commit 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-102343-4-eNMjvW4VcF@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).