From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19882 invoked by alias); 6 Apr 2008 07:37:08 -0000 Received: (qmail 19871 invoked by uid 22791); 6 Apr 2008 07:37:07 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 06 Apr 2008 07:36:46 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m367aiJ3032130 for ; Sun, 6 Apr 2008 03:36:44 -0400 Received: from pobox.stuttgart.redhat.com (pobox.stuttgart.redhat.com [172.16.2.10]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m367ahIJ001685 for ; Sun, 6 Apr 2008 03:36:44 -0400 Received: from hridell.englab.brq.redhat.com (hridell.englab.brq.redhat.com [10.34.32.30]) by pobox.stuttgart.redhat.com (8.13.1/8.13.1) with ESMTP id m367ahm9011054 for ; Sun, 6 Apr 2008 03:36:43 -0400 Date: Mon, 07 Apr 2008 02:06:00 -0000 From: Petr Machata To: frysk@sourceware.org Subject: Shortcomings of HPD '#' identifier qualification syntax Message-ID: <20080406073643.GB14265@hridell.englab.brq.redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00029.txt.bz2 --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 871 HPD syntax misses certain features that I'd like to use in ftrace (and who knows, maybe fhpd users would appreciate them, too). So here goes my bikeshed problem: 1) You can't specify ELF symbol version, 2) You can't specify PLT entry Number 1 can be solved by simply allowing the symbol name to have a form of "symbolname@version". "@" is good for that purpose, because it's non-ambiguous, and already used by readelf to refer to symbol versions. Number 2 can be resolved in any number of ways. In ftrace, I currently output traced PLT entries like "#soname#plt:symbolname". This looks nice, seems to be easy to remember, but would be hard to parse in the context of ?: ternary expression. objdump uses notation of the form of "symbol@PLT", which would collide with symbol version syntax. Maybe something along the lines of ".plt:symbol"? Opinions? Ideas? PM --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFH+H2LT6tJy0SVQPIRAr8tAJ9v7iQ5TFKiRGGpX5bujLha2VXW0gCeNY3S 1rwLB5oCit529QFAsAHsqzI= =4iZo -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK--