public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52592] [4.7/4.8 Regression] compilation failure with undefined reference to `__builtin_iround' Date: Thu, 15 Mar 2012 07:11:00 -0000 [thread overview] Message-ID: <bug-52592-4-1DF5a6jMWM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52592-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52592 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-03-15 06:43:55 UTC --- Reduced testcase: int best_state[256][256]; __attribute__((cold)) int encode_init(double p) { return best_state[(int)round(p)][0]; } --- CUT --- (define_expand "lround<X87MODEF:mode><SWI248x:mode>2" [(match_operand:SWI248x 0 "nonimmediate_operand" "") (match_operand:X87MODEF 1 "register_operand" "")] "(TARGET_USE_FANCY_MATH_387 && (!(SSE_FLOAT_MODE_P (<X87MODEF:MODE>mode) && TARGET_SSE_MATH) || TARGET_MIX_SSE_I387) && flag_unsafe_math_optimizations) || (SSE_FLOAT_MODE_P (<X87MODEF:MODE>mode) && TARGET_SSE_MATH && <SWI248x:MODE>mode != HImode && ((<SWI248x:MODE>mode != DImode) || TARGET_64BIT) && !flag_trapping_math && !flag_rounding_math)" { if (optimize_insn_for_size_p ()) FAIL; --- CUT --- Looks like there is a disconnect about when choosing iround over lround. I bet the code that handles the expanding of __builtin_iround (expand_builtin_int_roundingfn_2) should do exactly what the expanding of iceil does (expand_builtin_int_roundingfn).
next prev parent reply other threads:[~2012-03-15 6:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-15 5:40 [Bug c/52592] New: mplayer " ojab at ojab dot ru 2012-03-15 6:02 ` [Bug c/52592] " pinskia at gcc dot gnu.org 2012-03-15 6:04 ` [Bug middle-end/52592] " pinskia at gcc dot gnu.org 2012-03-15 6:04 ` ojab at ojab dot ru 2012-03-15 6:13 ` ojab at ojab dot ru 2012-03-15 6:13 ` [Bug middle-end/52592] [4.7/4.8 Regression] " pinskia at gcc dot gnu.org 2012-03-15 6:44 ` pinskia at gcc dot gnu.org 2012-03-15 7:11 ` pinskia at gcc dot gnu.org [this message] 2012-03-15 7:22 ` pinskia at gcc dot gnu.org 2012-03-15 7:47 ` pinskia at gcc dot gnu.org 2012-03-15 9:42 ` jakub at gcc dot gnu.org 2012-03-15 13:41 ` jakub at gcc dot gnu.org 2012-03-15 13:42 ` jakub at gcc dot gnu.org 2012-03-15 14:18 ` jakub 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-52592-4-1DF5a6jMWM@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).