public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin.liska at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/57703] Assembler function definition moved to a different ltrans then call
Date: Tue, 18 Mar 2014 16:05:00 -0000	[thread overview]
Message-ID: <bug-57703-4-vVQtEHV0h4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57703-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57703

--- Comment #4 from Martin Liška <marxin.liska at gmail dot com> ---
Hm, it looks that there's an usage of top-level function chromium binary:

/tmp/cckAZyDK.ltrans26.ltrans.o:cckAZyDK.ltrans26.o:function
sandbox::Die::ExitGroup(): error: undefined reference to 'SyscallAsm'
/tmp/cckAZyDK.ltrans26.ltrans.o:cckAZyDK.ltrans26.o:function
sandbox::Die::ExitGroup(): error: undefined reference to 'SyscallAsm'
/tmp/cckAZyDK.ltrans26.ltrans.o:cckAZyDK.ltrans26.o:function
sandbox::Die::SandboxDie(char const*, char const*, int): error: undefined
reference to 'SyscallAsm'
/tmp/cckAZyDK.ltrans26.ltrans.o:cckAZyDK.ltrans26.o:function
sandbox::Trap::SigSys(int, siginfo_t*, void*): error: undefined reference to
'SyscallAsm'


SyscallAsm:
namespace playground2 {

  asm volatile(
# 76 "../../sandbox/linux/seccomp-bpf/syscall.cc"
            ".text\n"
            ".align 16, 0x90\n"
            ".type SyscallAsm, @function\n"
 "SyscallAsm:.cfi_startproc\n"




            "test %rax, %rax\n"
            "jge  1f\n"


            "call 0f;   .cfi_adjust_cfa_offset  8\n"
          "0:pop  %rax; .cfi_adjust_cfa_offset -8\n"
            "addq $2f-0b, %rax\n"
            "ret\n"




          "1:movq  0(%r12), %rdi\n"
            "movq  8(%r12), %rsi\n"
            "movq 16(%r12), %rdx\n"
            "movq 24(%r12), %r10\n"
            "movq 32(%r12), %r8\n"
            "movq 40(%r12), %r9\n"

            "syscall\n"

          "2:ret\n"
            ".cfi_endproc\n"
          "9:.size SyscallAsm, 9b-SyscallAsm\n"
# 172 "../../sandbox/linux/seccomp-bpf/syscall.cc"
  );

If it's not supported feature, how could we handle such situation in LTO?
Assembler functions are commong in all kind video/audio codecs which are often
added to firefox/chromium.

Martin
>From gcc-bugs-return-446734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 18 16:22:19 2014
Return-Path: <gcc-bugs-return-446734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32488 invoked by alias); 18 Mar 2014 16:22:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32457 invoked by uid 48); 18 Mar 2014 16:22:15 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60566] New: [4.9 Regression] r208573 miscompiles kdelibs
Date: Tue, 18 Mar 2014 16:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: trippels at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-60566-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg01603.txt.bz2
Content-length: 704

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`566

            Bug ID: 60566
           Summary: [4.9 Regression] r208573 miscompiles kdelibs
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: trippels at gcc dot gnu.org
                CC: jason at gcc dot gnu.org

kdelibs gets miscompiled with current trunk.
Bisection points to r208573.

Symptoms of the miscompilation are startup failures of various KDE application,
e.g. okular will show a pop-up "Cannot connect to okular component" and
hang.
Will look deeper tomorrow.


  parent reply	other threads:[~2014-03-18 16:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 20:49 [Bug lto/57703] New: " marxin.liska at gmail dot com
2013-06-25  8:00 ` [Bug lto/57703] " rguenth at gcc dot gnu.org
2013-06-26 12:45 ` marxin.liska at gmail dot com
2014-03-18 16:05 ` marxin.liska at gmail dot com [this message]
2014-03-19 11:03 ` rguenth at gcc dot gnu.org
2014-03-25 10:39 ` jamborm at gcc dot gnu.org
2014-09-06 10:21 ` trippels at gcc dot gnu.org
2014-09-06 10:29 ` trippels at gcc dot gnu.org
2014-12-28  8:52 ` trippels at gcc dot gnu.org
2014-12-28 10:17 ` amonakov at gcc dot gnu.org
2020-09-21  0:03 ` egallager at gcc dot gnu.org
2020-09-21  7:12 ` marxin at gcc dot gnu.org
2022-01-01 22:58 ` pinskia 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-57703-4-vVQtEHV0h4@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).