public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65244] Bogus -Wmaybe-uninitialized warning with posix_memalign() and -Og
Date: Sat, 28 Feb 2015 01:24:00 -0000 [thread overview]
Message-ID: <bug-65244-4-yUhYfi2cPu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65244-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65244
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC|manu at gcc dot gnu.org |
Known to work| |4.8.2, 5.0
--- Comment #11 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
I don't have GCC 4.9.1 to try, but I would assume it is confirmed according to
Jack.
If it did not trigger in 4.8, then it is technically a regression.
__builtin_posix_memalign was introduced in r207595.
>From gcc-bugs-return-478807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 27 23:04:23 2015
Return-Path: <gcc-bugs-return-478807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114830 invoked by alias); 27 Feb 2015 23:04:23 -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 114562 invoked by uid 48); 27 Feb 2015 23:04:19 -0000
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65244] Bogus -Wmaybe-uninitialized warning with posix_memalign() and -Og
Date: Sat, 28 Feb 2015 05:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: howarth at bromo dot med.uc.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65244-4-m4IPlh4fgR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65244-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65244-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-02/txt/msg03139.txt.bz2
Content-length: 207
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide244
--- Comment #12 from howarth at bromo dot med.uc.edu ---
The issue also exists in current gcc-4_9-branch but applying r217317 doesn't
eliminate it there.
next prev parent reply other threads:[~2015-02-27 22:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 18:51 [Bug c/65244] New: " ulfalizer at gmail dot com
2015-02-27 19:10 ` [Bug c/65244] " ulfalizer at gmail dot com
2015-02-27 21:02 ` manu at gcc dot gnu.org
2015-02-27 21:24 ` ulfalizer at gmail dot com
2015-02-27 21:48 ` manu at gcc dot gnu.org
2015-02-27 22:02 ` ulfalizer at gmail dot com
2015-02-27 22:07 ` howarth at bromo dot med.uc.edu
2015-02-27 23:04 ` ulfalizer at gmail dot com
2015-02-27 23:21 ` pinskia at gcc dot gnu.org
2015-02-28 1:24 ` manu at gcc dot gnu.org [this message]
2021-03-31 19:05 ` [Bug middle-end/65244] " msebor at gcc dot gnu.org
2022-08-30 8:27 ` [Bug tree-optimization/65244] " rguenth at gcc dot gnu.org
2022-08-31 9:07 ` rguenth at gcc dot gnu.org
2022-08-31 11:04 ` cvs-commit at gcc dot gnu.org
2022-08-31 11:04 ` rguenth 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-65244-4-yUhYfi2cPu@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).