public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96566] [nvptx] Timeout in gcc.dg/builtin-object-size-21.c
Date: Tue, 11 Aug 2020 12:06:44 +0000 [thread overview]
Message-ID: <bug-96566-4-esjHOowu01@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96566-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96566
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> If we run the command by hand, and tail the .s file, we get an endless
> repetition of 0, 0, 0, ... , which starts off like this:
> ...
> // BEGIN GLOBAL VAR DEF: xm3_3
> .visible .global .align 1 .u32 xm3_3[-2305843009213693951]
> = { 0, 0, 0,
> ...
>
> The negative length doesn't look good.
Using:
...
diff --git a/gcc/config/nvptx/nvptx.c b/gcc/config/nvptx/nvptx.c
index cf53a921e5b..752c12561dd 100644
--- a/gcc/config/nvptx/nvptx.c
+++ b/gcc/config/nvptx/nvptx.c
@@ -2232,7 +2232,7 @@ nvptx_assemble_decl_begin (FILE *file, const char *name,
const char *section,
if (size)
/* We make everything an array, to simplify any initialization
emission. */
- fprintf (file, "[" HOST_WIDE_INT_PRINT_DEC "]", init_frag.remaining);
+ fprintf (file, "[" HOST_WIDE_INT_PRINT_UNSIGNED "]", init_frag.remaining);
else if (atype)
fprintf (file, "[]");
}
...
we have instead:
...
.visible .global .align 1 .u32 xm3_3[16140901064495857665]
...
which in hex is 0xE000000000000001, so it still looks wrong.
next prev parent reply other threads:[~2020-08-11 12:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 11:27 [Bug target/96566] New: " vries at gcc dot gnu.org
2020-08-11 11:55 ` [Bug target/96566] " vries at gcc dot gnu.org
2020-08-11 12:06 ` vries at gcc dot gnu.org [this message]
2020-08-11 12:09 ` jakub at gcc dot gnu.org
2020-08-11 12:10 ` jakub at gcc dot gnu.org
2020-08-11 12:12 ` vries at gcc dot gnu.org
2020-08-11 13:32 ` vries at gcc dot gnu.org
2020-08-11 13:47 ` jakub at gcc dot gnu.org
2020-08-11 13:53 ` vries at gcc dot gnu.org
2020-08-11 13:56 ` vries at gcc dot gnu.org
2020-08-11 14:20 ` msebor at gcc dot gnu.org
2020-08-11 14:37 ` vries at gcc dot gnu.org
2020-08-11 16:19 ` vries at gcc dot gnu.org
2020-08-12 10:42 ` vries at gcc dot gnu.org
2020-08-12 11:06 ` vries at gcc dot gnu.org
2020-08-12 12:05 ` cvs-commit at gcc dot gnu.org
2020-08-12 12:45 ` vries at gcc dot gnu.org
2020-08-12 12:52 ` vries at gcc dot gnu.org
2020-08-12 12:53 ` vries 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-96566-4-esjHOowu01@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).