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 target/107731] loongarch Operand Modifiers are not documented
Date: Tue, 24 Jan 2023 04:56:07 +0000	[thread overview]
Message-ID: <bug-107731-4-29n1YsKfER@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107731-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by LuluCheng <chenglulu@gcc.gnu.org>:

https://gcc.gnu.org/g:b5ea0f071aca505c82cc8c062e57bf9892900277

commit r13-5319-gb5ea0f071aca505c82cc8c062e57bf9892900277
Author: Lulu Cheng <chenglulu@loongson.cn>
Date:   Wed Jan 18 11:06:56 2023 +0800

    LoongArch: Fixed a compilation failure with '%c' in inline assembly
[PR107731].

    Co-authored-by: Yang Yujie <yangyujie@loongson.cn>

            PR target/107731

    gcc/ChangeLog:

            * config/loongarch/loongarch.cc (loongarch_classify_address):
            Add precessint for CONST_INT.
            (loongarch_print_operand_reloc): Operand modifier 'c' is supported.
            (loongarch_print_operand): Increase the processing of '%c'.
            * doc/extend.texi: Adds documents for LoongArch operand modifiers.
            And port the public operand modifiers information to this document.

    gcc/testsuite/ChangeLog:

            * gcc.target/loongarch/tst-asm-const.c: Moved to...
            * gcc.target/loongarch/pr107731.c: ...here.

  parent reply	other threads:[~2023-01-24  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  6:45 [Bug target/107731] New: error: invalid 'asm': invalid use of '%c' chenglulu at loongson dot cn
2022-11-17  7:38 ` [Bug target/107731] loongarch Operand Modifiers are not documented pinskia at gcc dot gnu.org
2022-11-17  7:40 ` xry111 at gcc dot gnu.org
2022-11-17  7:41 ` pinskia at gcc dot gnu.org
2022-11-17  7:44 ` pinskia at gcc dot gnu.org
2022-11-17  7:47 ` xry111 at gcc dot gnu.org
2022-11-17  7:50 ` chenglulu at loongson dot cn
2022-11-17  7:54 ` chenglulu at loongson dot cn
2023-01-24  4:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-24  5:00 ` chenglulu at loongson dot cn

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-107731-4-29n1YsKfER@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).