public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tneumann at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/109670] [13/14 regression] Exception handling broken for 32-bit Windows
Date: Wed, 10 May 2023 10:52:06 +0000	[thread overview]
Message-ID: <bug-109670-4-eLojNVqKo6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109670-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Thomas Neumann <tneumann at users dot sourceforge.net> ---
Created attachment 55037
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55037&action=edit
radix sort fix

I could reproduce the problem, the radix sort did not behave correctly when we
ran out of bits, which can happen on 32bit platforms. The attached patch fixes
the problem.

  parent reply	other threads:[~2023-05-10 10:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 16:43 [Bug ada/109670] New: SYSTEM.PERFECT_HASH_GENERATORS.TOO_MANY_TRIES compilation error on 32bit Windows starting with GCC 13 reiter.christoph at gmail dot com
2023-04-28 17:02 ` [Bug ada/109670] " reiter.christoph at gmail dot com
2023-04-28 18:22 ` reiter.christoph at gmail dot com
2023-04-28 18:29 ` reiter.christoph at gmail dot com
2023-04-28 20:41 ` reiter.christoph at gmail dot com
2023-05-03 20:53 ` reiter.christoph at gmail dot com
2023-05-06  6:00 ` [Bug libgcc/109670] Exception handling broken for " lh_mouse at 126 dot com
2023-05-06  6:50 ` reiter.christoph at gmail dot com
2023-05-08 12:54 ` tneumann at users dot sourceforge.net
2023-05-08 14:23 ` lh_mouse at 126 dot com
2023-05-08 14:33 ` tneumann at users dot sourceforge.net
2023-05-09  1:06 ` lh_mouse at 126 dot com
2023-05-09  8:00 ` [Bug libgcc/109670] [13/14 regression] Exception handling broken for 32-bit Windows ebotcazou at gcc dot gnu.org
2023-05-10 10:52 ` tneumann at users dot sourceforge.net [this message]
2023-05-12  9:37 ` lh_mouse at 126 dot com
2023-05-12 15:13 ` lh_mouse at 126 dot com
2023-05-13 23:12 ` reiter.christoph at gmail dot com
2023-06-03  7:47 ` cvs-commit at gcc dot gnu.org
2023-06-03  7:57 ` cvs-commit at gcc dot gnu.org
2023-07-12 14:10 ` mikpelinux at gmail dot com
2023-07-12 14:34 ` tneumann at users dot sourceforge.net
2023-07-12 14:38 ` xry111 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-109670-4-eLojNVqKo6@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).