public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5802] avr: Fix AVR build [PR71934] Date: Mon, 6 Dec 2021 10:21:05 +0000 (GMT) [thread overview] Message-ID: <20211206102105.ED3A23858D28@sourceware.org> (raw) https://gcc.gnu.org/g:4dc6d19222581c77a174d44d97507d234fb7e39b commit r12-5802-g4dc6d19222581c77a174d44d97507d234fb7e39b Author: Jakub Jelinek <jakub@redhat.com> Date: Mon Dec 6 11:18:58 2021 +0100 avr: Fix AVR build [PR71934] On Mon, Dec 06, 2021 at 11:00:30AM +0100, Martin Liška wrote: > Jakub, I think the patch broke avr-linux target: > > g++ -fno-PIE -c -g -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-erro > /home/marxin/Programming/gcc/gcc/config/avr/avr.c: In function ‘void avr_output_data_section_asm_op(const void*)’: > /home/marxin/Programming/gcc/gcc/config/avr/avr.c:10097:26: error: invalid conversion from ‘const void*’ to ‘const char*’ [-fpermissive] This patch fixes that. 2021-12-06 Jakub Jelinek <jakub@redhat.com> PR pch/71934 * config/avr/avr.c (avr_output_data_section_asm_op, avr_output_bss_section_asm_op): Change argument type from const void * to const char *. Diff: --- gcc/config/avr/avr.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/config/avr/avr.c b/gcc/config/avr/avr.c index 6ba038881d6..1c2f7d564e7 100644 --- a/gcc/config/avr/avr.c +++ b/gcc/config/avr/avr.c @@ -10089,7 +10089,7 @@ avr_asm_asm_output_aligned_bss (FILE *file, tree decl, const char *name, to track need of __do_copy_data. */ static void -avr_output_data_section_asm_op (const void *data) +avr_output_data_section_asm_op (const char *data) { avr_need_copy_data_p = true; @@ -10102,7 +10102,7 @@ avr_output_data_section_asm_op (const void *data) to track need of __do_clear_bss. */ static void -avr_output_bss_section_asm_op (const void *data) +avr_output_bss_section_asm_op (const char *data) { avr_need_clear_bss_p = true;
reply other threads:[~2021-12-06 10:21 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=20211206102105.ED3A23858D28@sourceware.org \ --to=jakub@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: 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).