From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Antoni Boucher <bouanto@zoho.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: [PATCH] libgccjit: Add ability to get the alignment of a type
Date: Fri, 28 Jun 2024 13:50:36 +0200 [thread overview]
Message-ID: <ydda5j570c3.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <c518116dfc2069482a05d59f14c36c236fb31daf.camel@redhat.com> (David Malcolm's message of "Wed, 26 Jun 2024 11:16:43 -0400")
David Malcolm <dmalcolm@redhat.com> writes:
> On Thu, 2024-04-04 at 18:59 -0400, Antoni Boucher wrote:
>> Hi.
>> This patch adds a new API to produce an rvalue representing the
>> alignment of a type.
>> Thanks for the review.
>
> Patch looks good to me (but may need the usual ABI version updates when
> merging).
This patch broke macOS bootstrap:
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc: In member function 'virtual gcc::jit::recording::string* gcc::jit::recording::memento_of_typeinfo::make_debug_string()':
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc:5529:30: error: 'ident' may be used uninitialized [-Werror=maybe-uninitialized]
5529 | return string::from_printf (m_ctxt,
| ~~~~~~~~~~~~~~~~~~~~^~~~~~~~
5530 | "%s (%s)",
| ~~~~~~~~~~
5531 | ident,
| ~~~~~~
5532 | m_type->get_debug_string ());
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc:5519:15: note: 'ident' was declared here
5519 | const char* ident;
| ^~~~~
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc: In member function 'virtual void gcc::jit::recording::memento_of_typeinfo::write_reproducer(gcc::jit::reproducer&)':
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc:5552:11: error: 'type' may be used uninitialized [-Werror=maybe-uninitialized]
5552 | r.write (" gcc_jit_rvalue *%s =\n"
| ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
5553 | " gcc_jit_context_new_%sof (%s, /* gcc_jit_context *ctxt */\n"
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5554 | " (gcc_jit_type *) %s); /* gcc_jit_type *type */\n",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5555 | id,
| ~~~
5556 | type,
| ~~~~~
5557 | r.get_identifier (get_context ()),
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5558 | r.get_identifier (m_type));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
/vol/gcc/src/hg/master/darwin/gcc/jit/jit-recording.cc:5541:15: note: 'type' was declared here
5541 | const char* type;
| ^~~~
I wonder how this can have worked anywhere (apart from jit not being
enabled by default on non-Darwin targets).
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2024-06-28 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 22:59 Antoni Boucher
2024-06-26 15:16 ` David Malcolm
2024-06-28 11:50 ` Rainer Orth [this message]
2024-06-29 1:28 ` Iain Sandoe
2024-06-29 2:54 ` Iain Sandoe
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=ydda5j570c3.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=bouanto@zoho.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@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).