public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/110179] unwind-dw2-fde-dip.c:406: assignment makes integer from pointer without a cast
Date: Tue, 11 Jul 2023 04:21:29 +0000	[thread overview]
Message-ID: <bug-110179-4-rWd6lwqoe6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110179-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110179

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@gcc.gnu.org>:

https://gcc.gnu.org/g:104b09005229ef48a79a33511ea192bb3ec3c415

commit r14-2426-g104b09005229ef48a79a33511ea192bb3ec3c415
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Jul 11 06:19:39 2023 +0200

    libgcc: Fix -Wint-conversion warning in find_fde_tail

    Fixes commit r14-1614-g49310a99330849 ("libgcc: Fix eh_frame fast path
    in find_fde_tail").

    libgcc/

            PR libgcc/110179
            * unwind-dw2-fde-dip.c (find_fde_tail): Add cast to avoid
            implicit conversion of pointer value to integer.

  parent reply	other threads:[~2023-07-11  4:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 16:27 [Bug libgcc/110179] New: " dcb314 at hotmail dot com
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 [this message]
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-rWd6lwqoe6@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: 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).