unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Florian Weimer (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: [review v2] hurd: Fix GCC 10 -Warray-bounds warning in init-first.c
Date: Fri, 15 Nov 2019 12:38:44 -0500	[thread overview]
Message-ID: <20191115173844.81A3620AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1573839493000.Ided58244ca0ee48892519faac5ac222a4e02dec4@gnutoolchain-gerrit.osci.io>

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/657
......................................................................

hurd: Fix GCC 10 -Warray-bounds warning in init-first.c

The trampoline code should really be rewritten in assembler because
this is all very undefined at the C level.

Change-Id: Ided58244ca0ee48892519faac5ac222a4e02dec4
---
M sysdeps/mach/hurd/i386/init-first.c
1 file changed, 10 insertions(+), 0 deletions(-)



diff --git a/sysdeps/mach/hurd/i386/init-first.c b/sysdeps/mach/hurd/i386/init-first.c
index f1f1c40..286d2a0 100644
--- a/sysdeps/mach/hurd/i386/init-first.c
+++ b/sysdeps/mach/hurd/i386/init-first.c
@@ -30,6 +30,7 @@
 
 #include <ldsodefs.h>
 #include <fpu_control.h>
+#include <libc-diag.h>
 
 extern void __mach_init (void);
 extern void __init_misc (int, char **, char **);
@@ -144,9 +145,16 @@
 static inline void
 init (int *data)
 {
+  /* data is the address of the argc parameter to _dl_init_first or
+     doinit1 in _hurd_stack_setup, so the array subscripts are
+     undefined.  */
+  DIAG_PUSH_NEEDS_COMMENT;
+  DIAG_IGNORE_NEEDS_COMMENT (10, "-Warray-bounds");
+
   int argc = *data;
   char **argv = (void *) (data + 1);
   char **envp = &argv[argc + 1];
+
   struct hurd_startup_data *d;
 
   /* Since the cthreads initialization code uses malloc, and the
@@ -265,6 +273,8 @@
 	 restored by function return.  */
       asm volatile ("# a %0 c %1" : : "a" (usercode), "c" (&init1));
     }
+
+  DIAG_POP_NEEDS_COMMENT;	/* -Warray-bounds.  */
 }
 
 /* These bits of inline assembler used to be located inside `init'.

-- 
Gerrit-Project: glibc
Gerrit-Branch: master
Gerrit-Change-Id: Ided58244ca0ee48892519faac5ac222a4e02dec4
Gerrit-Change-Number: 657
Gerrit-PatchSet: 2
Gerrit-Owner: Florian Weimer <fweimer@redhat.com>
Gerrit-MessageType: newpatchset

  reply	other threads:[~2019-11-15 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 17:38 [review] hurd: Fix GCC 10 -Warray-bounds warning in init-first.c Florian Weimer (Code Review)
2019-11-15 17:38 ` Florian Weimer (Code Review) [this message]
2019-11-15 17:39 ` [review v3] " Florian Weimer (Code Review)
2019-11-15 17:40 ` [review v4] hurd: Suppress " Florian Weimer (Code Review)
2019-11-15 17:50 ` [review v5] hurd: Suppress GCC 10 -Warray-bounds warning in init-first.c [BZ #25097] Florian Weimer (Code Review)
2019-11-16 11:55   ` Samuel Thibault
2019-11-16 14:50 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-16 14:50 ` Sourceware to Gerrit sync (Code Review)

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191115173844.81A3620AF6@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).