public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: ewlu@rivosinc.com
Cc: jeffreyalaw@gmail.com, gcc-patches@gcc.gnu.org,
	gnu-toolchain@rivosinc.com, Vineet Gupta <vineetg@rivosinc.com>
Subject: Re: [Committed] riscv: generate builtin macro for compilation with strict alignment:
Date: Tue, 29 Aug 2023 08:53:40 -0700 (PDT)	[thread overview]
Message-ID: <mhng-e5ead1e9-d6c0-4c0d-8211-f11ae7f0335d@palmer-ri-x1c9a> (raw)
In-Reply-To: <eb8d898a-3558-4289-8c7d-37575d812ad2@rivosinc.com>

On Tue, 29 Aug 2023 08:48:56 PDT (-0700), ewlu@rivosinc.com wrote:
>
> On 8/28/2023 3:40 PM, Jeff Law wrote:
>>
>>
>> On 8/15/23 12:29, Edwin Lu wrote:
>>> This patch is a modification of
>>> https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610115.html
>>> following the discussion on
>>> https://github.com/riscv-non-isa/riscv-c-api-doc/issues/32
>>>
>>> Distinguish between explicit -mstrict-align and cpu tune param
>>> for slow_unaligned_access=true/false.
>>>
>>> Tested for regressions using rv32/64 multilib with newlib/linux
>>>
>>> gcc/ChangeLog:
>>>
>>>     * config/riscv/riscv-c.cc (riscv_cpu_cpp_builtins):
>>>       Generate __riscv_unaligned_avoid with value 1 or
>>>               __riscv_unaligned_slow with value 1 or
>>>               __riscv_unaligned_fast with value 1
>>>     * config/riscv/riscv.cc (riscv_option_override):
>>>      Define riscv_user_wants_strict_align. Set
>>>      riscv_user_wants_strict_align to TARGET_STRICT_ALIGN
>>>     * config/riscv/riscv.h: Declare riscv_user_wants_strict_align
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>>     * gcc.target/riscv/attribute-1.c: Check for
>>>      __riscv_unaligned_slow or __riscv_unaligned_fast
>>>     * gcc.target/riscv/attribute-4.c: Check for
>>>      __riscv_unaligned_avoid
>>>     * gcc.target/riscv/attribute-5.c: Check for
>>>      __riscv_unaligned_slow or __riscv_unaligned_fast
>>>     * gcc.target/riscv/predef-align-1.c: New test.
>>>     * gcc.target/riscv/predef-align-2.c: New test.
>>>     * gcc.target/riscv/predef-align-3.c: New test.
>>>     * gcc.target/riscv/predef-align-4.c: New test.
>>>     * gcc.target/riscv/predef-align-5.c: New test.
>>>     * gcc.target/riscv/predef-align-6.c: New test.
>> OK.  Though I'm pretty sure the commit hooks are going to complain 
>> about your ChangeLog :-)
>>
>> jeff
>
> I did need to do some ChangeLog formatting but was able to commit it in 
> the end :)

There's a gcc-commit-mklog git hook script in contrib/ that should do 
most of the formatting for you.

>
> Edwin
>
> -- 
> You received this message because you are subscribed to the Google Groups "gnu-toolchain" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gnu-toolchain+unsubscribe@rivosinc.com.
> To view this discussion on the web visit https://groups.google.com/a/rivosinc.com/d/msgid/gnu-toolchain/eb8d898a-3558-4289-8c7d-37575d812ad2%40rivosinc.com.
> For more options, visit https://groups.google.com/a/rivosinc.com/d/optout.

  reply	other threads:[~2023-08-29 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 18:29 [PATCH V3] " Edwin Lu
2023-08-28 22:40 ` Jeff Law
2023-08-29 15:48   ` [Committed] " Edwin Lu
2023-08-29 15:53     ` Palmer Dabbelt [this message]
2023-08-29 16:12       ` Edwin Lu

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=mhng-e5ead1e9-d6c0-4c0d-8211-f11ae7f0335d@palmer-ri-x1c9a \
    --to=palmer@dabbelt.com \
    --cc=ewlu@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=vineetg@rivosinc.com \
    /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).