public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Georg-Johann Lay <gjl@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-8345] AVR: Document option -mskip-bug.
Date: Tue, 20 Feb 2024 11:46:47 +0000 (GMT)	[thread overview]
Message-ID: <20240220114647.237B93858C42@sourceware.org> (raw)

https://gcc.gnu.org/g:1ee33557d97d68899503e5e111cc851b3e99f667

commit r13-8345-g1ee33557d97d68899503e5e111cc851b3e99f667
Author: Georg-Johann Lay <avr@gjlay.de>
Date:   Mon Jan 15 17:06:58 2024 +0100

    AVR: Document option -mskip-bug.
    
    gcc/
            * doc/invoke.texi (AVR Options) [-mskip-bug]: Add documentation.
    
    (cherry picked from commit 42503cc257fb841904917c9529f24c76511c4e0d)

Diff:
---
 gcc/doc/invoke.texi | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 63f5170f69e9..8f52302d0752 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -864,7 +864,7 @@ Objective-C and Objective-C++ Dialects}.
 -mn_flash=@var{size}  -mno-interrupts
 -mmain-is-OS_task  -mrelax  -mrmw  -mstrict-X  -mtiny-stack
 -mfract-convert-truncate
--mshort-calls  -nodevicelib  -nodevicespecs
+-mshort-calls  -mskip-bug  -nodevicelib  -nodevicespecs
 -Waddr-space-convert  -Wmisspelled-isr}
 
 @emph{Blackfin Options}
@@ -23294,6 +23294,12 @@ Assume that @code{RJMP} and @code{RCALL} can target the whole
 program memory. This option is used for multilib generation and selection
 for the devices from architecture @code{avrxmega3}.
 
+@opindex mskip-bug
+@item -mskip-bug
+
+Generate code without skips (@code{CPSE}, @code{SBRS},
+@code{SBRC}, @code{SBIS}, @code{SBIC}) over 32-bit instructions.
+
 @opindex msp8
 @item -msp8
 Treat the stack pointer register as an 8-bit register,

                 reply	other threads:[~2024-02-20 11:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240220114647.237B93858C42@sourceware.org \
    --to=gjl@gcc.gnu.org \
    --cc=gcc-cvs@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).