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 go/103847] gccgo SIGSEGV in libgo standard library on sparc64
Date: Wed, 29 Dec 2021 23:53:37 +0000 [thread overview]
Message-ID: <bug-103847-4-YeI2i2jWJs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103847-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103847
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>:
https://gcc.gnu.org/g:62c3f75fd29e93054f3aeb8a623fd52c98c3db0b
commit r12-6147-g62c3f75fd29e93054f3aeb8a623fd52c98c3db0b
Author: Ian Lance Taylor <iant@golang.org>
Date: Wed Dec 29 15:08:32 2021 -0800
compiler, libgo: don't pad sparc64-linux epollevent
Change the compiler to not add zero padding because of zero-sized
fields named "_", since those can't be referenced anyhow.
Change the sparc-linux64 epollevent struct to name the alignment
field "_", to avoid zero padding.
Fixes PR go/103847
PR go/103847
* godump.c (go_force_record_alignment): Name the alignment
field "_".
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/374914
next prev parent reply other threads:[~2021-12-29 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 22:59 [Bug go/103847] New: " matoro_gcc_bugzilla at matoro dot tk
2021-12-27 23:00 ` [Bug go/103847] " matoro_gcc_bugzilla at matoro dot tk
2021-12-27 23:00 ` matoro_gcc_bugzilla at matoro dot tk
2021-12-27 23:01 ` matoro_gcc_bugzilla at matoro dot tk
2021-12-28 17:47 ` ian at airs dot com
2021-12-29 0:53 ` matoro_gcc_bugzilla at matoro dot tk
2021-12-29 2:49 ` ian at airs dot com
2021-12-29 3:05 ` matoro_gcc_bugzilla at matoro dot tk
2021-12-29 23:53 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-30 18:43 ` ian at airs dot com
2022-01-01 5:32 ` cvs-commit at gcc dot gnu.org
2022-01-07 6:38 ` pinskia 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-103847-4-YeI2i2jWJs@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).