From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org, Luis Machado <luis.machado@arm.com>
Subject: Re: [PATCH] Fix various procfs.c compilation errors
Date: Wed, 16 Nov 2022 10:30:50 -0700 [thread overview]
Message-ID: <87bkp6u7qt.fsf@tromey.com> (raw)
In-Reply-To: <ydda64r7xig.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Wed, 16 Nov 2022 16:02:47 +0100")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> procfs.c has accumulated several compilation errors lately (some of them
Rainer> new with GCC 12), which are fixed by this patch:
Thank you.
Rainer> It seems that this is another case of GCC PR middle-end/88059, which
Rainer> Martin Sebor refuses to fix. So I'm using the hack suggested in the
Rainer> PR to use memcpy instead of strncpy.
FWIW it's also fine to change this code to use std::string, which is
probably both simpler to understand and will avoid warnings. Up to you
though.
Tom
next prev parent reply other threads:[~2022-11-16 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:02 Rainer Orth
2022-11-16 15:53 ` Simon Marchi
2022-11-17 9:46 ` Rainer Orth
2022-11-16 17:30 ` Tom Tromey [this message]
2022-11-17 9:48 ` Rainer Orth
2022-11-16 19:04 ` Luis Machado
2022-11-17 9:50 ` Rainer Orth
2022-11-17 10:08 ` Luis Machado
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=87bkp6u7qt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).