public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14736] New: [tree-ssa] code quality regression Date: Thu, 25 Mar 2004 23:20:00 -0000 [thread overview] Message-ID: <20040325231958.14736.dann@godzilla.ics.uci.edu> (raw) There seems to be a code quality regression in tree-ssa between 2004/03/08 and 2004/03/20 The .vars dump for generate-3.4.ii from PR8361 generated by gcc version 3.5-tree-ssa 20040308 (merged 20040305) has 100840 lines the one generated by gcc version 3.5-tree-ssa 20040320 (merged 20040307) has 85811 lines. Granted the number of lines in .vars is not the best measure of code quality, but given the 15% size difference something seems wrong. Looking at the diff between the 2 I saw the following type of difference in a few places: <L5>:; - if (__result == __first) goto <L6>; else goto <L7>; + se = (struct ELEMENT &)__first; + if (__result == (struct ELEMENT * const)se) goto <L6>; else goto <L7>; Given that this code is from std::vector::iterator it appears in quite a few places. Look for example at: typename std::vector<_Tp, _Alloc>::iterator std::vector<_Tp, _Alloc>::erase(__gnu_cxx::__normal_iterator<_Tp*, std::vector<_Tp, _Alloc> >, __gnu_cxx::__normal_iterator<_Tp*, std::vector<_Tp, _Alloc> >) [with _Tp = STACK<int>::ELEMENT, _Alloc = std::allocator<STACK<int>::ELEMENT>] (this, __first, __last) Another oddity is code like: <L38>:; __first = __first; __result = __result; -- Summary: [tree-ssa] code quality regression Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P2 Component: optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dann at godzilla dot ics dot uci dot edu CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14736
next reply other threads:[~2004-03-25 23:20 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-25 23:20 dann at godzilla dot ics dot uci dot edu [this message] 2004-03-25 23:34 ` [Bug optimization/14736] " pinskia at gcc dot gnu dot org 2004-04-06 19:15 ` pinskia at gcc dot gnu dot org 2004-05-17 0:14 ` [Bug tree-optimization/14736] " pinskia at gcc dot gnu dot org 2004-05-17 13:41 ` pinskia at gcc dot gnu dot org 2004-06-02 4:32 ` pinskia at gcc dot gnu dot org 2004-06-02 4:33 ` pinskia at gcc dot gnu dot org 2004-06-02 4:41 ` pinskia at gcc dot gnu dot org 2004-06-02 17:38 ` dann at godzilla dot ics dot uci dot edu 2004-06-02 18:57 ` cvs-commit at gcc dot gnu dot org 2004-06-02 19:00 ` pinskia at gcc dot gnu dot org 2004-06-02 19:58 ` pinskia at gcc dot gnu dot 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=20040325231958.14736.dann@godzilla.ics.uci.edu \ --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).