From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 366 invoked by alias); 14 Apr 2012 04:39:03 -0000 Received: (qmail 32679 invoked by uid 22791); 14 Apr 2012 04:39:01 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-pz0-f49.google.com (HELO mail-pz0-f49.google.com) (209.85.210.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 14 Apr 2012 04:38:46 +0000 Received: by dadq36 with SMTP id q36so4615028dad.22 for ; Fri, 13 Apr 2012 21:38:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:x-gm-message-state; bh=drXc8lwDIzhkAAjg3l0qIgnS/6NKAalWwkU5o+HsiJw=; b=ld7ECTQcF+OCa2vGV/qqFL3mFF21q921/vs68QIBytPlWGMLXgprKuB9SBBzxZ0J9c ZasgdM2TNWTOyDTmegI5YM4cyf7doCz3DQ8ULo6U3gT3AAcgnLThbCXajolbEwoQC84Y jpKD9U58GcKbUk73K816FqO9sjTXPDyZRabuxL9q8SQzD7nup1J9qPJOxWkyG+flZYms JQj7vJ7MmMVmwWNCjlyzgJjn6VRAtHW3y+c4gjjLBNoS1C+vR06RnC4QFJO2pydBOEIV +7/JG6N2W1g5uqtYUH8verAsJy/BJH/shW/qo2zdzWCRMMgXZECBjeTiamNR5p4l5tVj NK/w== Received: by 10.68.136.40 with SMTP id px8mr4550216pbb.8.1334378325236; Fri, 13 Apr 2012 21:38:45 -0700 (PDT) Received: by 10.68.136.40 with SMTP id px8mr4550203pbb.8.1334378325095; Fri, 13 Apr 2012 21:38:45 -0700 (PDT) Received: from coign.google.com (rrcs-76-79-72-18.west.biz.rr.com. [76.79.72.18]) by mx.google.com with ESMTPS id i5sm10655942pbf.19.2012.04.13.21.38.44 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 Apr 2012 21:38:44 -0700 (PDT) From: Ian Lance Taylor To: Amir Ghanbari Cc: gcc-help@gcc.gnu.org Subject: Re: Add assembly instruction to GCC References: Date: Sat, 14 Apr 2012 04:39:00 -0000 In-Reply-To: (Amir Ghanbari's message of "Fri, 13 Apr 2012 09:24:13 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Gm-Message-State: ALoCoQmgpWlOEB16llkaQbw9mBlFjGN8rImUG74JIQB2eweyg16fUuaADpqRRdNUAklnNopt+zJpaqL72lK6wcATT4JWwlG0KHTmxpV1gyIGJKnrd+AwBOIrrO4tG/ihW7z4BfbM0MeQQ+fUtDf1ydMfqYUwPnci5hq2xrwF6YBgXCOoDQDqpgs= X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-04/txt/msg00159.txt.bz2 Amir Ghanbari writes: > The problem is that the binary being generated is not exactly what I > want. What is the precise byte sequence that you want, and what is the precise byte sequence that you are getting? Don't show us the disassembly; show us the bytes. > I need to make GCC > treat that "F0 0F 23" as an instruction and put it in the binary > intact and don't mix it with other instructions. I'm sorry, I don't know what this means. GCC generates assembly code and the assembler generates bytes. Ian