public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yufan8.chen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/60947] [4.9/4.10 Regression] Unable to handle kernel paging request (linux kernel 2.6.28.9) with gcc 4.9 release Date: Thu, 24 Apr 2014 03:43:00 -0000 [thread overview] Message-ID: <bug-60947-4-sIk8RhmV3N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60947-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60947 --- Comment #5 from YuFan <yufan8.chen at gmail dot com> --- (In reply to Andrew Pinski from comment #4) > Could there be an out of bounds access in that loop? I traced the code, and the following code is equal to the original one with replacing inline functions. In C code, there would be no possibility to get an out of bounds access. #SNDRV_PCM_HW_PARAM_FIRST_MASK 0 #SNDRV_PCM_HW_PARAM_LAST_MASK 2 for (k = SNDRV_PCM_HW_PARAM_FIRST_MASK; k <= SNDRV_PCM_HW_PARAM_LAST_MASK; k++) { memset(&constrs->masks[k - SNDRV_PCM_HW_PARAM_FIRST_MASK], 0xff, SNDRV_MASK_SIZE * sizeof(u_int32_t)); } > Can you try adding -fno-vrp? I supposed you mean -fno-tree-vrp. I tried it but still has the same issue. The following assembly code snippet is the same as the original one without -fno-tree-vrp =============================================== snd_pcm_hw_constraints_init: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 1, uses_anonymous_args = 0 mov ip, sp stmfd sp!, {r4, r5, r6, r7, r8, r9, r10, fp, ip, lr, pc} sub fp, ip, #4 sub sp, sp, #20 ldr r8, [r0, #112] add r3, r8, #232 add r4, r8, #328 .L1062: mov r0, r3 mov r1, #255 mov r2, #8 bl memset add r3, r0, #32 cmp r3, r4 bne .L1062 mov r3, #0 mov r2, r8 mov r5, r3 mov r4, #12 mvn lr, #0 ===============================================
next prev parent reply other threads:[~2014-04-24 3:43 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-24 2:24 [Bug rtl-optimization/60947] New: [4.9 " yufan8.chen at gmail dot com 2014-04-24 2:25 ` [Bug rtl-optimization/60947] " yufan8.chen at gmail dot com 2014-04-24 2:27 ` yufan8.chen at gmail dot com 2014-04-24 2:27 ` yufan8.chen at gmail dot com 2014-04-24 2:28 ` [Bug rtl-optimization/60947] [4.9/4.10 " pinskia at gcc dot gnu.org 2014-04-24 3:43 ` yufan8.chen at gmail dot com [this message] 2014-04-24 9:00 ` rguenth at gcc dot gnu.org 2014-04-24 10:01 ` yufan8.chen at gmail dot com 2014-04-24 10:17 ` trippels at gcc dot gnu.org 2014-04-24 10:45 ` yufan8.chen at gmail dot com 2014-04-24 11:22 ` rguenth at gcc dot gnu.org 2014-04-28 9:35 ` yufan8.chen at gmail dot com 2014-05-02 5:31 ` yufan8.chen at gmail dot com 2014-06-25 5:32 ` amker at gcc dot gnu.org 2014-06-25 8:06 ` amker at gcc dot gnu.org 2014-06-25 8:17 ` amker at gcc dot gnu.org 2014-06-26 2:14 ` amker at gcc dot gnu.org 2014-06-26 8:36 ` amker at gcc dot gnu.org 2014-06-26 9:48 ` amker at gcc dot gnu.org 2014-06-30 8:20 ` yufan8.chen at gmail dot com
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-60947-4-sIk8RhmV3N@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: linkBe 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).