From: Ben Widawsky <ben@bwidawsk.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] Drop "-Wunsafe-loop-optimizations".
Date: Thu, 02 Aug 2012 17:47:41 -0700 [thread overview]
Message-ID: <e8363491d90462cdf858c413dfac1ba1@bwidawsk.net> (raw)
In-Reply-To: <1343932193-27192-1-git-send-email-eric@anholt.net>
On 2012-08-02 11:29, Eric Anholt wrote:
> It warns about totally sensible things done in intel_decode.c. I've
> never seen this warn do anything useful, and apparently I was the one
> to introduce it when I added the giant pile of warning flags back in
> 2008.
> ---
> configure.ac | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> index 09fed53..3eaec74 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -133,7 +133,7 @@ MAYBE_WARN="-Wall -Wextra \
> -Wpointer-arith -Wwrite-strings -Wstrict-prototypes \
> -Wmissing-prototypes -Wmissing-declarations -Wnested-externs \
> -Wpacked -Wswitch-enum -Wmissing-format-attribute \
> --Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations \
> +-Wstrict-aliasing=2 -Winit-self \
> -Wdeclaration-after-statement -Wold-style-definition \
> -Wno-missing-field-initializers -Wno-unused-parameter \
> -Wno-attributes -Wno-long-long -Winline"
If you're interested:
http://lists.freedesktop.org/archives/dri-devel/2012-June/024636.html
prev parent reply other threads:[~2012-08-03 0:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 18:29 [PATCH 1/3] Drop "-Wunsafe-loop-optimizations" Eric Anholt
2012-08-02 18:29 ` [PATCH 2/3] intel: Import updated i915_drm.h Eric Anholt
2012-08-03 0:49 ` Ben Widawsky
2012-08-06 17:59 ` Eric Anholt
2012-08-02 18:29 ` [PATCH 3/3] intel: Add a function for the new register read ioctl Eric Anholt
2012-08-03 0:55 ` Ben Widawsky
2012-08-03 0:47 ` Ben Widawsky [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=e8363491d90462cdf858c413dfac1ba1@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.