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 modula2/109315] typo: inconsistant
Date: Wed, 29 Mar 2023 16:39:25 +0000	[thread overview]
Message-ID: <bug-109315-4-YteHURs4E9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109315-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109315

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>:

https://gcc.gnu.org/g:3be4e43a6a0f429648ea188c8e110b74268fed27

commit r13-6931-g3be4e43a6a0f429648ea188c8e110b74268fed27
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date:   Wed Mar 29 17:38:22 2023 +0100

    PR modula2/109336 - The -fmod= and -fdef= options do not work

    The -fmod= and -fdef= options do not work.  After the linking
    re-implementation and subsequent restructuring the -fmod= amd -fdef= are
    now broken.  This patch adds -fmod= and -fdef= processing into gm2spec.cc.
    It also reduces the complexity of extension handling within M2Search
    by storing the preceeding "." in the extension.

    gcc/m2/ChangeLog:

            PR modula2/109336
            PR modula2/109315
            * gm2-compiler/M2FileName.mod (CalculateFileName): Simplified by
            ensuring the extension contains the ".".
            (CalculateStemName): Re-formatted.
            (ExtractExtension): Re-formatted.
            (ExtractModule): Re-formatted.
            * gm2-compiler/M2Options.def (setdefextension): Add block comment.
            (setmodextension): Add block comment.  Re-formatted.
            * gm2-compiler/M2Options.mod (setdefextension): Add block comment.
            (setmodextension): Add block comment.  Re-formatted.
            * gm2-compiler/M2Search.mod (FindSourceDefFile): Use
            DefaultDefExt.
            (DefaultDefExt): New constant.
            (DefaultModExt): New constant.
            (FindSourceModFile): Use DefaultModExt.
            * gm2-gcc/m2decl.cc (m2decl_DeclareKnownVariable): Correct
            spelling.
            * gm2spec.cc (M2SOURCE): New constant.
            (LANGSPEC): New value.
            (MATHLIB): New value.
            (WITHLIBC): New value.
            (SKIPOPT): New value.
            (lang_specific_driver): Replace seen_module_extension bool with
            module_extension char *.  Detect -fmod= and remember extension.
            Use the extension to detect modula-2 source and mark it as such.

    gcc/testsuite/ChangeLog:

            PR modula2/109336
            * gm2/link/nondefaultext/pass/hello.md: New test.
            * gm2/link/nondefaultext/pass/liba.dm: New test.
            * gm2/link/nondefaultext/pass/liba.md: New test.
            * gm2/link/nondefaultext/pass/link-nondefaultext-pass.exp: New
test.

    Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>

  parent reply	other threads:[~2023-03-29 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  8:09 [Bug modula2/109315] New: " roland.illig at gmx dot de
2023-03-28 15:01 ` [Bug modula2/109315] " gaius at gcc dot gnu.org
2023-03-29 16:39 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-29 16:40 ` gaius 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-109315-4-YteHURs4E9@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: 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).