From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E0FD43858D1E; Sun, 26 Feb 2023 12:34:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E0FD43858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677414849; bh=A8PiI/4GkEijqjReLNFzedXBnE4brlyRdzoRdYVJyh0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dY17pLi3aVObYndZ+1bVjcfw4CS8aJG45m6C/eUXYLf9ucWgZO9lW26YSKma1Qw7f 7YEVtcfM7rPU9UvPTmFbdBNSZUHpes0I8d3o1vwpwEhJFlfw6qxmMarlmwG3rKJEIS oeSmNUg3du2aAxBDRwdMRifH+AJMPF9EWZNZq4/4= From: "uaa at mx5 dot nisiq.net" To: gcc-bugs@gcc.gnu.org Subject: [Bug demangler/107884] H8/300: cp-demangle.c fix warning related demangle.h Date: Sun, 26 Feb 2023 12:34:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: demangler X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uaa at mx5 dot nisiq.net X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107884 --- Comment #9 from SASANO Takayoshi --- (In reply to Michael N. Moran from comment #8) > I created a corresponding cp-demangle.s file and attached it > https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54530 Please read this thread carefully, currently this issue targets=20 H8 advanced mode (24bit address). Your attachment says that the code is compiled for H8 normal mode (16bit address). > .file "cp-demangle.c" > .h8300hn > .section .text But, we have to consider why the problem has occurred. > .Ldebug_ranges3: > .section .debug_line,"",@progbits > .Ldebug_line0: > .2byte 0, .LELT0-.LSLT0 > .LSLT0: > .2byte 0x5 (snip) >=20=20 > .byte 0x1 > .LELT0: > .section .debug_str,"MS",@progbits,1 > .LASF248: (.LELT0 - .LSLT0) shows the size of .debug_line section. The reported problem means "allocated bitwidth for .Ldebug_line0 is insufficient to store the size of .debug_line section". I think this is out of topic, should be handled at more suitable place.=