From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109669 invoked by alias); 16 Jan 2018 16:47:53 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 109657 invoked by uid 89); 16 Jan 2018 16:47:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=whitelist, Hx-languages-length:2256 X-HELO: mail-wm0-f51.google.com Received: from mail-wm0-f51.google.com (HELO mail-wm0-f51.google.com) (74.125.82.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Jan 2018 16:47:47 +0000 Received: by mail-wm0-f51.google.com with SMTP id i11so9898394wmf.4 for ; Tue, 16 Jan 2018 08:47:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Y5gNXYfr4sd668hUb18uRw+vJfivHduSkvYvJ8NtOBk=; b=s7r+1+6k6Vu6VBGYrg980Tu16e1DOmDXVEh4zybwO9vxCxzZAJxr1XE3+hd9OLPLqR Ebk9xX/mlzCCXUn2+C4n3qBGMqZjpRk4ix+1JgB3LKJdZQy4f7kH94Z4L57RJ9/JbKsy CchXTpcSjZgqFSvhbj7LX0oRnGlvLMPH3KS5T6l3/lxIjG6DoZ/gChnISbgj8bYUkb7c bjT0KOsE+J2ZWegkgiZqu8Z2VQ/aKs/1ITXr1dSFXd192b/BI4xN9Jh2mVg99OsSyniZ R8hACOfPfUtaWRBJLcuWmGpL2naol5UgNe1YKeUqsfqjqLnbOWNnJ8N6fMAe8QHzQPOp A5bQ== X-Gm-Message-State: AKwxytdRqgQZ7Saf/jmrpON0L7ElQKNWoZyISAMsYyci9834feCB9INr sM7+83QWxSBmDC+tPVv3XsG5QcUN7Xc= X-Google-Smtp-Source: ACJfBouBZlhz7x1nCP6AUHI25E36bONUqu1NOOiITYgfJpkPn4I3MNxzhIOFAw7VdnOk22MTPuWX0A== X-Received: by 10.28.107.134 with SMTP id a6mr14046960wmi.136.1516121264822; Tue, 16 Jan 2018 08:47:44 -0800 (PST) Received: from ?IPv6:2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4? ([2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4]) by smtp.gmail.com with ESMTPSA id w83sm2698572wma.47.2018.01.16.08.47.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jan 2018 08:47:43 -0800 (PST) Subject: Re: [PATCH] Run gdb.compile/*.exp on {x86,x86_64,s390}-linux only To: Yao Qi , Pedro Alves Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com References: <1516103412-25086-1-git-send-email-yao.qi@linaro.org> <088c44b5-5454-e187-3984-956a30904ffc@redhat.com> <86k1whg7iy.fsf@gmail.com> From: Phil Muldoon Message-ID: Date: Tue, 16 Jan 2018 16:47:00 -0000 MIME-Version: 1.0 In-Reply-To: <86k1whg7iy.fsf@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-01/txt/msg00306.txt.bz2 On 16/01/18 15:14, Yao Qi wrote: > Pedro Alves writes: > > People need to implement these "compile" related gdbarch methods to > support this feature. Also, we also need to "port" it to the distro > other than Fedora/RHEL, I've never get it working on Ubuntu. What were the problems? I don't work on the compile project any more but AFAIK we made it distro neutral. > searching for compiler matching regex ^aarch64(-[^-]*)?-linux(-gnu)?-gcc$^M > found compiler /home/yaoqi01/fsf-trunk-build/build-native-aarch64-none-linux-gnu/install/sysroot/usr/bin/aarch64-none-linux-gnu-gcc^M > Passing 11 compiler options:^M > Compiler option 0: <>^M > Compiler option 1: <-std=gnu11>^M > Compiler option 2: <-fno-exceptions>^M > Compiler option 3: <-O0>^M > Compiler option 4: <-gdwarf-4>^M > Compiler option 5: <-fPIE>^M > Compiler option 6: <-Wall>^M > Compiler option 7: <-Wno-implicit-function-declaration>^M > Compiler option 8: <-Wno-unused-but-set-variable>^M > Compiler option 9: <-Wno-unused-variable>^M > Compiler option 10: <-fno-stack-protector>^M > source file produced: /tmp/gdbobj-6vzbkt/out3.c^M > ^M > aarch64-none-linux-gnu-gcc: error: : No such file or directory The only thing I can think of is either path or ld_library_path is not set or not installed in those locations. >>> I think we need to properly skip tests on targets which don't support >>> compile. As far as I know, gdb compile is supported on x86, x86_64, >>> and s390. However, I see no problem with a whitelist, even if it is disliked. > See my post above. The issue isn't as simple as "having -m64 > in target options". It is known that compile feature works on > x86/fedora, and my dest is aarch64/ubuntu. The gap is not small. > Probably, it can be broke into two steps, x86/fedora -> x86/ubuntu -> > aarch64/ubuntu, or x86/fedora -> aarch64/fedora -> aarch64/ubuntu. > I am in a stage that triage all test fails on aarch64 and arm with > recent gcc, and I don't have an immediate plan to support compile on > aarch64-linux and arm-linux. I don't think I've ever tried it on arm. I think, if memory serves, that Tom tried it on a Debian setup. Still, it *should* work. Cheers Phil