Sponsored Content
Top Forums Programming How Can a Machine Reads a Compiler Since A Compiler is Written in Text! Not Binaries? Post 302257995 by f.ben.isaac on Thursday 13th of November 2008 02:24:28 PM
Old 11-13-2008
Quote:
Originally Posted by shamrock
That's the job of the assembler. It converts hex strings to machine code in the instruction set of the mpu and ofcourse the separation of data and instructions.

Can you give an example of instruction set of the mpu? Does it look like:
ADD, JMP, etc? If yes, then ADD need to be translated too unless if it inserted directly as 110010 101001 (ADD #), something like that....

Ok assume, we wrote the code from the keyboard in binaries, so kept writing such as 101001 110110 10110100, refers to ADD AX, etc. Can my machine just grab this binaries without the help of any compiler?

I guess the only way to fully understand it, i have to take hardware, and compiler construction courses.

Anyway, I appreciate all of your help members! Well Said, Well Answered
 

We Also Found This Discussion For You

1. Programming

C compiler to build Sparc/Solaris binaries on Linux

Just that the Subject says. I am looking for a C compiler for Linux x86 that will allow me to compile a C source code file and the resulting binary will be able to run on a Sparc running Solaris. Thanks. (2 Replies)
Discussion started by: lyonsd
2 Replies
ALTER FOREIGN DATA 
WRAPPER(7) SQL Commands ALTER FOREIGN DATA WRAPPER(7) NAME
ALTER FOREIGN DATA WRAPPER - change the definition of a foreign-data wrapper SYNOPSIS
ALTER FOREIGN DATA WRAPPER name [ VALIDATOR valfunction | NO VALIDATOR ] [ OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ]) ] ALTER FOREIGN DATA WRAPPER name OWNER TO new_owner DESCRIPTION
ALTER FOREIGN DATA WRAPPER changes the definition of a foreign-data wrapper. The first form of the command changes the library or the generic options of the foreign-data wrapper (at least one clause is required). The second form changes the owner of the foreign-data wrap- per. Only superusers can alter foreign-data wrappers. Additionally, only superusers can own foreign-data wrappers. PARAMETERS
name The name of an existing foreign-data wrapper. VALIDATOR valfunction Specifies a new foreign-data wrapper validator function. Note that it is possible that after changing the validator the options to the foreign-data wrapper, servers, and user mappings have become invalid. It is up to the user to make sure that these options are correct before using the foreign-data wrapper. NO VALIDATOR This is used to specify that the foreign-data wrapper should no longer have a validator function. OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] ) Change options for the foreign-data wrapper. ADD, SET, and DROP specify the action to be performed. ADD is assumed if no operation is explicitly specified. Option names must be unique; names and values are also validated using the foreign data wrapper library. EXAMPLES
Change a foreign-data wrapper dbi, add option foo, drop bar: ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar'); Change the foreign-data wrapper dbi validator to bob.myvalidator: ALTER FOREIGN DATA WRAPPER dbi VALIDATOR bob.myvalidator; COMPATIBILITY
ALTER FOREIGN DATA WRAPPER conforms to ISO/IEC 9075-9 (SQL/MED). The standard does not specify the VALIDATOR and OWNER TO variants of the command. SEE ALSO
CREATE FOREIGN DATA WRAPPER [create_foreign_data_wrapper(7)], DROP FOREIGN DATA WRAPPER [drop_foreign_data_wrapper(7)] SQL - Language Statements 2010-05-14 ALTER FOREIGN DATA WRAPPER(7)
All times are GMT -4. The time now is 11:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy