public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/110179] New: unwind-dw2-fde-dip.c:406: assignment makes integer from pointer without a cast Date: Thu, 08 Jun 2023 16:27:13 +0000 [thread overview] Message-ID: <bug-110179-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110179 Bug ID: 110179 Summary: unwind-dw2-fde-dip.c:406: assignment makes integer from pointer without a cast Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- I just tried a build of gcc trunk with clang 16.04 on x86_64. It said: libgcc/unwind-dw2-fde-dip.c:406:16: warning: assignment to ‘_Unwind_Ptr’ {aka ‘long unsigned int’} from ‘const unsigned char *’ makes integer from pointer without a cast [-Wint-conversion] Git blame says: 49310a9933 (Florian Weimer 2023-06-06 11:01:07 +0200 406) eh_frame = p + value; This warning might be worth fixing. I suspect a cast will do it.
next reply other threads:[~2023-06-08 16:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-08 16:27 dcb314 at hotmail dot com [this message] 2023-06-08 16:37 ` [Bug libgcc/110179] " dcb314 at hotmail dot com 2023-06-09 6:26 ` egallager at gcc dot gnu.org 2023-07-10 11:55 ` fw at gcc dot gnu.org 2023-07-11 4:21 ` cvs-commit at gcc dot gnu.org 2023-07-11 4:54 ` fw at gcc dot gnu.org 2023-07-18 15:02 ` cvs-commit at gcc dot gnu.org
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-110179-4@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: 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).