Sponsored Content
Top Forums UNIX for Beginners Questions & Answers A function that refuses to run anywhere else but main() Post 303032024 by bakunin on Saturday 9th of March 2019 05:12:38 PM
Old 03-09-2019
Quote:
Originally Posted by ignatius
I know, that it is a big "NO NO" to use code that is generated by a source code converter, but, i'd rather not use the shell script in my code, just standard C code. So, that is my reasoning for that. Maybe that's the problem right there?
Source code converters are OK, in and on themselves, but the problem begins when you try to edit the generated code. Code created by a generator is usually understandable only to the compiler - most likely even the generator is confused reading what it has produced. You don't create an assembler listing from compiled code and change that in assembler either (at least not as long hell is not overbooked and you are sentenced to doing this for your sins instead).

Let us take a step back: what is the reason you don't want to use a shell script? Maybe there is a way to solve this problem without using this abomination in what C was never intended to look like.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. Programming

c++ calling main() function

i just finished a project for a c++ class that i wrote at home on my computer, compiled with gcc. when i brought the code into school it would not compile, it would complain that cannot call main() function. at school we use ancient borland c++ from 1995. anyway my program has 20 different... (3 Replies)
Discussion started by: norsk hedensk
3 Replies

2. Programming

main function

Is it possible to execute any function before main() function in C or C++. (6 Replies)
Discussion started by: arun.viswanath
6 Replies

3. Programming

signal handling while in a function other than main

Hi, I have a main loop which calls a sub loop, which finally returns to the main loop itself. The main loop runs when a flag is set. Now, I have a signal handler for SIGINT, which resets the flag and thus stops the main loop. Suppose I send SIGINT while the program is in subloop, I get an error... (1 Reply)
Discussion started by: Theju
1 Replies

4. Shell Programming and Scripting

Help in separating variables declared in the main function

Hi! I've a C program as shown below.. The line numbers and the statements of the program are separated by a space.. 1 #include<stdio.h> 2 char a,b,c; 3 float x,y,z; 4 int main() 5 { 6 int d,e,f; 7 // further declarations 8 // further declarations 9 /* body*/ 10 } 11 void fun1() 12... (1 Reply)
Discussion started by: abk07
1 Replies

5. Programming

unable to send a char parameter from main to a function

why does this not work? #include <stdio.h> #include <stdlib.h> char getFileMode(char charChanger) { char filetype; /*var to hold the value to be returned*/ filetype = charSetter; /*set filetype to "l" if it is a symlink*/ return filetype; } int main(void){ char... (8 Replies)
Discussion started by: bluetxxth
8 Replies

6. Programming

How to access argv[x] from another function other than main???

Hi friends, when I am passing arguments to main, I want another function to be able to have access to that function, the problem is that I am creating athread, which has a function like void *xyz(void *), how can pass the refernce of argv to this function, if you see my program, you will better... (2 Replies)
Discussion started by: gabam
2 Replies

7. Programming

Function main returning int?

H friends, As we know, a function returns a value and that value is saved somwhere. like int Sum( int x, int y ) { return x + y; } Total = Sum( 10, 20 ); The value 30 is saved in variable Total. Now the question is, what int value does the function main return, and where is it... (5 Replies)
Discussion started by: gabam
5 Replies

8. AIX

Calling functions from main program from dlopened library function

Hello All, I am trying to call a function from the calling main program from a dlopened library function, below is the entire code, when I execute it it crashes with sigill. Can you guys help me out I guess I am missing out on the linker flag or something here. besides I am new to AIX and... (1 Reply)
Discussion started by: syedtoah
1 Replies

9. UNIX for Dummies Questions & Answers

[ksh93+] Array fed by function is empty when used in main.

I feel that i am missing something obvious but i can't find what is wrong. I have a script that is launching some functions with "&" and each call is feeding the array with a value. When all calls are finished I just want to retrieve the values of that array. It is looking like that : ... (5 Replies)
Discussion started by: bibou25
5 Replies

10. Programming

A single statement without main function in c

A sample.c file is written with only one single statement. main; Segmentation fault occurred when executed that file. Any statement other than main; is written, for example unix; then it won't compile. why is this behaviour ! (2 Replies)
Discussion started by: techmonk
2 Replies
bcc(1)							      General Commands Manual							    bcc(1)

NAME
bcc - Bruce's C compiler SYNOPSIS
bcc [-03EGNOPSVcegvwxW] [-Aas_option] [-Bexecutable_prefix] [-Ddefine] [-Uundef] [-Mc_mode] [-o outfile] [-ansi] [-Ccc1_option] [-Pcpp_option] [-Iinclude_dir] [-Lld_option] [-Ttmpdir] [-Qc386_option] [-ttext_segno] [ld_options] [infiles] DESCRIPTION
Bcc is a simple C compiler that produces 8086 assembler, in addition compiler compile time options allow 80386 or 6809 versions. The compiler understands traditional K&R C with just the restriction that bit fields are mapped to one of the other integer types. The default operation is to produce an 8086 executable called a.out from the source file. OPTIONS
-ansi Pass the C source through unprotoize after preprocessing and before code generation. This will allow some ansi C to be compiled but it is definitly NOT a true ansi-C compiler. -0 8086 target (works on 80386 host, but not 6809) -3 80386 target (may work on 8086 host, but not 6809) -A pass remainder of option to assembler (e.g. -A-l -Alistfile for a listing) -B prefix for executable search path (as usual; the search order is all paths specified using -B, in order, then the path given in the environment variable BCC_EXEC_PREFIX if that is set, then the compiled-in defaults (something like /usr/lib/bcc/ followed by /usr/bin/) -C pass remainder of option to bcc-cc1, see code generation options. -D preprocessor define -E produce preprocessor output to standard out. -G produce GCC objects (Same as -Mg) -Ixyz include search 'xyz' path -I don't add default include to search list -Lxyz add directory name 'xyz' to the head of the list of library directories searched -L don't add default library to search list -Md alters the arguments for all passes to produce MSDOS executable COM files. These are small model executables, use -i to get tiny model. -Mf sets bcc to pass the -c and -f arguments to the code generator for smaller faster code. Note this code is not compatible with the standard calling conventions so a different version of the C library is linked too. -Mc sets bcc to pass the -c argument to the code generator for smaller faster code. Note the standard libc is normally transparent to this, but there are exceptions. -Ms alters the arguments for all passes and selects C-library to produce standalone Linux-86 executables -Ml switches to i386-Linux code generator and library. This configuration accepts the -z flag to generate QMAGIC a.out files instead of the normal OMAGIC. -Mg switches to i386-Linux code generator and generates OMAGIC object files that can be linked with some versions of gcc; unfortunatly the most recent versions use 'collect2' to link and this crashes. -N makes the linker produce a native a.out file (Linux OMAGIC) if combined with -3 the executable will run under Linux-i386. -O optimize, call copt(1) to optimize 8086 code. Specifiers to choose which rules copt should use can be appended to the -O and the option can be repeated. -P produce preprocessor output with no line numbers to standard output. -Q pass full option to c386 (Only for c386 version) -S produce assembler file -T temporary directory (overrides previous value and default; default is from the environment variable TMPDIR if that is set, otherwise /tmp) -U preprocessor undefine -V print names of files being compiled -X pass remainder of option to linker (e.g. -X-Ofile is passed to the linker as -Ofile) -c produce object file -f turn on floating point support, no effect with i386, changes libc library with 8086 code. -g produce debugging info (ignored.) -o output file name follows (assembler, object or executable) (as usual) -p produce profiling info (ignored.) -t1 pass to the assembler to renumber the text segment for multi-segment programs. -v print names and args of subprocesses being run. Two or more -v's print names of files being unlinked. Three or more -v's print names of paths being searched. -w Supress any warning diagnostics. -W Turn on assembler warning messages. -x don't include crt0.o in the link. -i don't pass -i to the linker so that it will create an impure executable. Other options are passed to the linker, in particular -lx, -M, -m, -s, -H. CODE GENERATOR OPTIONS
These are all options that the code generator pass bcc-cc1 understands, only some will be useful for the -C option of bcc. -0 8086 target (works even on 80386 host, not on 6809) -3 80386 target (may work even on 8086 host, not on 6809) -D define (as usual) -E produce preprocessor output (as usual) -I include search path (as usual) -P produce preprocessor output with no line numbers (as usual) -c produce code with caller saving regs before function calls -d print debugging information in assembly output -f produce code with 1st argument passed in a register (AX, EAX or X) -l produce code for 2 3 1 0 long byte order (only works in 16-bit code), a special library of compiler helper functions is needed for this mode. -o assembler output file name follows -p produce (almost) position-independent code (only for the 6809) -t print source code in assembly output -w print what cc1 thinks is the location counter in assembly output All the options except -D, -I and -o may be turned off by following the option letter by a '-'. Options are processed left to right so the last setting has precedence. PREPROCESSOR DEFINES
The preprocessor has a number of manifest constants. __BCC__ 1 The compiler identifier, normally used to avoid compiler limitations. __FILE__ stringized name of current input file __LINE__ current line number __MSDOS__ 1 compiler is configured for generating MSDOS executable COM files. __STANDALONE__ 1 compiler is configured for generating standalone executables. __AS386_16__ 1 compiler is generating 16 bit 8086 assembler and the #asm keyword is available for including 8086 code. __AS386_32__ 1 compiler is generating 32 bit 80386 assembler and the #asm keyword is available for including 80386 code. __CALLER_SAVES__ 1 compiler calling conventions are altered so the calling function must save the SI and DI registers if they are in use (ESI and EDI on the 80386) __FIRST_ARG_IN_AX__ 1 compiler calling conventions are altered so the calling function is passing the first argument to the function in the AX (or EAX ) register. __LONG_BIG_ENDIAN__ 1 alters the word order of code generated by the 8086 compiler. These defines only occur in the 6809 version of the compiler. __AS09__ 1 compiler is generating 6809 code __FIRST_ARG_IN_X__ 1 the first argument to functions is passed in the X register. __POS_INDEPENDENT__ 1 the code generated is (almost) position independent. ENVIRONMENT
BCC_EXEC_PREFIX default directory to seach for compiler passes TMPDIR directory to place temporary files (default /tmp) DIRECTORIES
All the include, library and compiler components are stored under the /usr/lib/bcc directory under Linux-i386, this is laid out the same as a /usr filesystem and if bcc is to be the primary compiler on a system it should be moved there. The configuration for this is in the bcc.c source file only, all other executables are independent of location. The library installation also creates the file /usr/lib/liberror.txt, this path is hardcoded into the C library. The bcc executable itself, as86 and ld86 are in /usr/bin. SEE ALSO
as86(1), ld86(1), elksemu(1) BUGS
The bcc.c compiler driver source is very untidy. The linker, ld86, produces a broken a.out object file if given one input and the -r option this is so it is compatible with pre-dev86 versions. Nov, 1997 bcc(1)
All times are GMT -4. The time now is 09:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy