public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dirtyepic at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32893] New: zlib segfault in inflate_table() compiled w/ -O -msse2 ftree-vectorize
Date: Wed, 25 Jul 2007 20:22:00 -0000 [thread overview]
Message-ID: <bug-32893-10406@http.gcc.gnu.org/bugzilla/> (raw)
(In reply to comment #17)
> This looks like an unrelated problem - the vectorizer does not perform loop
> peeling here so it's not an issue of natural alignment. Lets open a separate PR
> for this one, unless there's already one open. In the meantime, would you
> please try this patch?:
>
> Index: tree-vectorizer.c
> ===================================================================
> *** tree-vectorizer.c (revision 126902)
> --- tree-vectorizer.c (working copy)
> *************** vect_can_force_dr_alignment_p (tree decl
> *** 1527,1533 ****
> PREFERRED_STACK_BOUNDARY is honored by all translation units.
> However, until someone implements forced stack alignment, SSE
> isn't really usable without this. */
> ! return (alignment <= PREFERRED_STACK_BOUNDARY);
> }
>
>
> --- 1527,1533 ----
> PREFERRED_STACK_BOUNDARY is honored by all translation units.
> However, until someone implements forced stack alignment, SSE
> isn't really usable without this. */
> ! return (alignment <= STACK_BOUNDARY);
> }
>
Hey Dorit. With this patch zlib appears to compile successfully. The loop is
vectorized with an "alignment of access forced using peeling" note and linked
apps no longer segfault.
I also tested using Andrew's patch from bug #16660 and always returning true in
vect_can_force_dr_alignment_p but it does not fix this error.
Let me know if I can provide any other info that would be useful to you.
--
Summary: zlib segfault in inflate_table() compiled w/ -O -msse2
ftree-vectorize
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dirtyepic at gentoo dot org
GCC build triplet: i686-linux-gnu
GCC host triplet: i686-linux-gnu
GCC target triplet: i686-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32893
next reply other threads:[~2007-07-25 20:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 20:22 dirtyepic at gentoo dot org [this message]
2007-07-25 20:43 ` [Bug target/32893] " dorit at gcc dot gnu dot org
2007-07-25 20:45 ` pinskia at gcc dot gnu dot org
2007-07-28 21:04 ` dorit at gcc dot gnu dot org
2007-08-01 11:36 ` dorit at gcc dot gnu dot org
2007-08-01 11:57 ` dorit at gcc dot gnu dot org
2007-08-14 17:46 ` jigorou3 at mail dot goo dot ne dot jp
2007-09-19 14:29 ` dorit at gcc dot gnu dot org
2007-09-20 6:49 ` ubizjak at gmail dot com
2007-09-20 6:51 ` ubizjak at gmail dot com
2007-09-20 10:43 ` jigorou3 at mail dot goo dot ne dot jp
2007-09-20 11:58 ` ubizjak at gmail dot com
2007-09-22 10:27 ` ubizjak at gmail dot com
2007-09-22 11:28 ` jigorou3 at mail dot goo dot ne dot jp
2007-09-23 6:00 ` dirtyepic at gentoo dot org
2007-09-23 6:23 ` dirtyepic at gentoo dot org
2007-10-03 18:53 ` dorit at gcc dot gnu dot org
2007-10-30 5:25 ` dorit at gcc dot gnu dot org
2008-01-26 0:06 ` rguenth at gcc dot gnu dot org
2008-01-28 14:35 ` dorit at gcc dot gnu dot org
2008-02-07 0:05 ` hjl dot tools at gmail dot com
2008-02-07 22:16 ` hjl dot tools at gmail dot com
2009-08-06 16:47 ` hjl dot tools at gmail dot com
2009-08-10 17:48 ` mahatma at eu dot by
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-32893-10406@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).