public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65991] maybe-unitialized - false positive
Date: Tue, 07 Jul 2015 09:20:00 -0000	[thread overview]
Message-ID: <bug-65991-4-ji1kIqBB3p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65991-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65991

--- Comment #5 from Дилян Палаузов <dilyan.palauzov at aegee dot org> ---
The problem does not appear anymore, since I upgraded gcc 4.9.2 -> 4.9.3 .
>From gcc-bugs-return-491631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 07 10:07:55 2015
Return-Path: <gcc-bugs-return-491631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60107 invoked by alias); 7 Jul 2015 10:07:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60017 invoked by uid 48); 7 Jul 2015 10:07:51 -0000
From: "xricht17 at stud dot fit.vutbr.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/14940] PCH largefile test fails on various platforms
Date: Tue, 07 Jul 2015 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: pch
X-Bugzilla-Version: 4.0.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xricht17 at stud dot fit.vutbr.cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-14940-4-7SHbhLkMA9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-14940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-14940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg00521.txt.bz2
Content-length: 2023

https://gcc.gnu.org/bugzilla/show_bug.cgi?id\x14940

--- Comment #49 from Martin Richter <xricht17 at stud dot fit.vutbr.cz> ---
(In reply to Martin Richter from comment #47)

My apologies, that patch is incorrect - `VirtualAlloc` still uses
`pch_VA_max_size` instead of `size`.
Some discussion about this bug and the reasoning behind the patch can be found
here:
https://sourceforge.net/p/mingw-w64/bugs/382/


Now the correct patch:

diff --git a/gcc/config/i386/host-mingw32.c b/gcc/config/i386/host-mingw32.c
index aa17378..631d9c4 100644
--- a/gcc/config/i386/host-mingw32.c
+++ b/gcc/config/i386/host-mingw32.c
@@ -42,9 +42,6 @@ static size_t mingw32_gt_pch_alloc_granularity (void);

 static inline void w32_error(const char*, const char*, int, const char*);

-/* FIXME: Is this big enough?  */
-static const size_t pch_VA_max_size  = 128 * 1024 * 1024;
-
 /* Granularity for reserving address space.  */
 static size_t va_granularity = 0x10000;

@@ -86,9 +83,6 @@ static void *
 mingw32_gt_pch_get_address (size_t size, int)
 {
   void* res;
-  size = (size + va_granularity - 1) & ~(va_granularity - 1);
-  if (size > pch_VA_max_size)
-    return NULL;

   /* FIXME: We let system determine base by setting first arg to NULL.
      Allocating at top of available address space avoids unnecessary
@@ -98,7 +92,7 @@ mingw32_gt_pch_get_address (size_t size, int)
      If we allocate at bottom we need to reserve the address as early
      as possible and at the same point in each invocation. */

-  res = VirtualAlloc (NULL, pch_VA_max_size,
+  res = VirtualAlloc (NULL, size,
                      MEM_RESERVE | MEM_TOP_DOWN,
                      PAGE_NOACCESS);
   if (!res)
@@ -148,7 +142,7 @@ mingw32_gt_pch_use_address (void *addr, size_t size, int
fd,

   /* Offset must be also be a multiple of allocation granularity for
      this to work.  We can't change the offset. */
-  if ((offset & (va_granularity - 1)) != 0 || size > pch_VA_max_size)
+  if ((offset & (va_granularity - 1)) != 0)
     return -1;


      parent reply	other threads:[~2015-07-07  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-03 13:23 [Bug lto/65991] New: " dilyan.palauzov at aegee dot org
2015-05-03 13:28 ` [Bug lto/65991] " trippels at gcc dot gnu.org
2015-05-03 13:54 ` dilyan.palauzov at aegee dot org
2015-05-06 12:31 ` trippels at gcc dot gnu.org
2015-07-07  9:20 ` dilyan.palauzov at aegee dot org [this message]

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-65991-4-ji1kIqBB3p@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).