Gpc January 2003

gpc@gnu.de

39 participants
52 discussions

Inefficiency of `mod'
by Emil Jerabek 26 Oct '10

26 Oct '10

Hi, during some debugging I noticed that GPC generates very hairy code for the `mod' operator with signed arguments. A closer look revealed that the code contains a lot of branching on conditions which can be determined on compile time, and most surprisingly, the value of X mod Y is recomputed _twice_, if X is negative. (I've attached a commented assembler dump.) This may be partially a back-end problem (CSE?), but I feel there's something wrong in the relevant code in gpc-common.c (build_pascal_binary_op) as well. `exp1 mod exp2' gets translated into something like exp2 <= 0 ? error : exp1 >= 0 ? exp1 mod exp2 : ((-exp1) mod exp2) == 0 ? 0 : exp2 - (-exp1) mod exp2 This arranges that both arguments supplied to the "internal mod" are non-negative, but this information is not passed on -- the arguments are still declared as signed types, which apparently makes the back-end to produce the mess it does. I've done a little test: the following replacement for `mod', which differs from the built-in one essentially just by the type-casts to `Cardinal', inline operator xmod (X, Y: Integer) = Z: Integer; begin if Y <= 0 then RuntimeError (714); if X >= 0 then Z := Cardinal (X) mod Y else begin Z := Cardinal (-X) mod Y; if Z <> 0 then Z := Y - Z end end; indeed generates a better code, it measures about 15% faster for positive X and more than twice faster for negative X. YMMV. If this is possible in user code, it should work in the compiler internals as well :) The result type of the whole `mod' expression looks dubious too. IIUIC, `exp1 mod exp2' inherits the type of exp1. Now, the result of `mod' is guaranteed to be nonnegative and to fit in the type of exp2 (or more precisely, it is in 0 .. High (type of (exp2)) - 1), whereas it needn't have anything to do with the type of exp1: consider var X, Z: Integer; Y: LongInt; begin X := -8; Y := High (LongInt); Z := X mod Y { -> overflow } end Or am I missing something? Emil (BTW, where is fjf434c.pas?)

10 16

Upper/lower case in identifiers
by Frank Heckenbach 22 May '03

22 May '03

As you probably know, GPC currently converts all identifiers to first letter upper-case/rest lower-case. Since this is often not nice, I plan to change this. This would affect at least the following things: - error messages - the file name chosen with `--transparent-file-names' (makes a difference only on case-sensitive file systems, i.e. not Dos/Windows); is this ok (to those who use this option)? - the file name prompt with external files without binding While I'm at it, it might be easy to add a warning if an identifier is used with varying case (something like `var Foo: Integer; [...] WriteLn (FOO)'). - Any ideas for the name of the option? (`-Widentifier-case'?) - Default? (I suppose off, though I think I myself would prefer on.) - Should it work across units/modules? Or should it be a tri-state option (never/current file/global)? Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707

8 8

Re: Conformant array curiosity
by Wood David 24 Mar '03

24 Mar '03

Frank, Thanks for your reply. I've managed to cut down the module to this very short module so I just get two errors, both - prior parameter's size depends on 'A': MODULE Test interface; export Test=(Test_proc); PROCEDURE Test_proc(List : ARRAY[a..b :INTEGER] OF DOUBLE); END. MODULE Test implementation; PROCEDURE Test_proc; BEGIN List[a]:= 2.3; List[2]:= 2.3; END; { Test_proc } END. The errors correspond to each assignment although the error line is the declaration. Sure enough, converting this to a unit fixes the problem: UNIT Test; Interface PROCEDURE Test_proc(List : ARRAY[a..b :INTEGER] OF DOUBLE); Implementation PROCEDURE Test_proc; BEGIN List[a]:= 2.3; List[2]:= 2.3; END; { Test_proc } END. Is the module syntax illegal or is it a bug? If it is a bug, at least you can take comfort in knowing it can kill the DEC Pascal compiler too! Regards David Wood, QinetiQ Farnborough The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful.

2 2

Range Checking
by Frank Heckenbach 05 Mar '03

05 Mar '03

Hi, after some friendly requests and discussion, I'm planning to implement range checking as one of the next major things in GPC (probably in Januaray, if nothing urgent gets in between ...). Note, I'm using "range checking" in the specific meaning I explained recently, not generally for all kinds of runtime checks, and not including overflow checking of arithmetic operations etc. (that will be a separate issue). Also, as I said before, I'll do an "easy" implementation. I'm still not convinced that anything more is worth the (big) effort when the programmer in the rare (AFAICS) cases where it matters could just as well use explicit types etc. to avoid checks where he doesn't want them. Since some of you have said they'd like to help, but can't code in the compiler itself, here are at least 2 chances: 1. Help finding all places where range checking must be applied In mean this from a Pascal point of view, covering, of course, all standards, dialects and extensions that GPC supports. So far I've found the following ones: - assignment to variables and function results, - value parameter passing to user-defined and built-in (e.g., `Chr', `FillChar', ...) routines, - array indexing (R/W), - array slice indexing (R/W), - `for' loop bounds, - conformant array range, - actual schema discriminants, - initialization of types, variables and typed constants, - `asm' targets 2. Write test programs Test programs should follow the guidelines in the manual. In particular, since most of the tests will check for errors, each one must be a separate test for each situation (each of the cases above plus any that others of you will come up with). For a way to test runtime errors see, e.g., fjf424d.pas. Range checking will be on by default, and can be switched on/off with the options `--[no-]range-checking' and the compiler directives `{$[no-]range-checking}', and `{$R+}', `{$R-}'. A complete set of tests should also test all of those. If you'd like to do so, please post a short note, so several of you won't duplicate efforts, but can coordinate. Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707

6 15

Basic problem on OS X : cannot import units
by Antoine Gautier 01 Feb '03

01 Feb '03

Hello all. I just installed gpc on OS X from the microbizz binaries. Simple programs compile ok, but not when I try to use units. Do I need to set env variables in the tcsh ? add a path to the units somewhere ? Thanks ! Here is an example (is ok without the USES) : [ip-98-110:~] antoine% cat test.pas program test; uses gpc; begin writeln ('Hello world'); end. [ip-98-110:~] antoine% gpc test.pas test.pas:3: module/unit interface `Gpc' could not be imported [ip-98-110:~] antoine% which gpc /usr/bin/gpc [ip-98-110:~] antoine% gpc -v Reading specs from /Developer/Pascal/gpc321d3/lib/gcc-lib/powerpc-apple-darwin6.3/3.2.1/ specs Configured with: ../gpc-3.2.1/configure --enable-languages=pascal,c --prefix=/Developer/Pascal/gpc321d3 Thread model: single gpc version 20021128, based on gcc-3.2.1 [ip-98-110:~] antoine% ls -la /Developer/Pascal/gpc321d3/lib/gcc-lib/powerpc-apple-darwin6.3/3.2.1/ units/dos.pas -rw-rw-rw- 1 antoine staff 23088 Jan 11 04:39 /Developer/Pascal/gpc321d3/lib/gcc-lib/powerpc-apple-darwin6.3/3.2.1/ units/dos.pas [ip-98-110:~] antoine%

3 4

Testsuite results for gpc on Mac OS X
by Adriaan van Os 01 Feb '03

01 Feb '03

Below are the results of the testsuite for gpc-20021128 with gcc-3.2.1 on Mac OS X.2.3 (Darwin 6.3). I can send in more information as needed. Regards, Adriaan van Os P.S. Same results with -gstabs -------------- [G4:~] adriaan% gpc -v Reading specs from /usr/local/gpc321d3/lib/gcc-lib/powerpc-apple-darwin6.3/3.2.1/specs Configured with: ../gpc-3.2.1/configure --enable-languages=c,pascal --prefix=/usr/local/gpc321d3 Thread model: single gpc version 20021128, based on gcc-3.2.1 [G4:~] adriaan% cd ~/gnu/testgpc/test [G4:~/gnu/testgpc/test] adriaan% make Running the GPC Test Suite. This may take a while ... rm -f *.dat *.o *.s *.gpm *.gpi *.gpd *.gpc core a.out stderr.out *.exe testmake.tmp dummy.c dummy.pas dummy.out diff_cr*.tmp fixcr fixcr.exe rm -f todo/a.out todo/*.exe todo/*.o todo/*.s todo/*.gpm todo/*.gpi todo/*.gpd todo/core { gpc --version | head -1; gpc --print-search-dirs | grep install | head -1; hostname || echo "unknown host"; } | \ sed -e 's,^,Testing ,;N;s,\n.*gcc-lib[/\], (,;s,[/\].*,),;N;s,\n, (,;s,$,),' Testing gpc 20021128, based on gcc-3.2.1 (powerpc-apple-darwin6.3) (G4.local.) echo "gpc -g -O3 -W -Wall -Wundef -Wpointer-arith -Wno-unused " gpc -g -O3 -W -Wall -Wundef -Wpointer-arith -Wno-unused PC="gpc" PFLAGS="--autobuild -g -O3 -W -Wall -Wundef -Wpointer-arith -Wno-unused " SRCDIR="." TEST_MAKE_FLAG=test-make-flag "./test_run" "*.pas" | "./test_sum" TEST agettext2test.pas: SKIPPED: libintl not installed TEST asmtest.pas: SKIPPED: only for IA32 TEST asmtest2.pas: SKIPPED: only for IA32 TEST asmtest3.pas: SKIPPED: only for IA32 TEST backtracerr.pas: 2c2,71 < ./test_run: line 188: 22183 Segmentation fault ./"$A_OUT" "$x" --- > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to b(c) > b: about to yy > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > c: about to a(yy) > a: about to xx() > d: > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > a: back from xx() > c: back from a(yy) > b: back from yy > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > b: back from b(c) > program: back from b( d ) failed TEST bill5.pas: SKIPPED: `attribute( section(".ltext") )' not available TEST dario.pas: SKIPPED: only for IA32 TEST fay.pas: 1c1,12 < ./test_run: line 188: 28960 Segmentation fault ./"$A_OUT" "$x" --- > stacking 1 > Doing successors of 1 > stacking 2 > Doing successors of 2 > Now checking if 2 is an SCC root > Now checking if 1 is an SCC root > 1 is an SCC root; SP= 2 T= 1 > Yield SCC should pass 1 out to TakeUSCC > YieldUSCC passes 1 to TakeUSCC > TakeUSCC receives V= 1 from YieldUSCC > The SCC's constituents are: > 2 1 failed TEST fjf165a.pas: SKIPPED: German locale not installed TEST fjf35.pas: ./test_run: line 199: 7712 Segmentation fault ./"$A_OUT" "$x" TEST fjf434a.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST fjf434ax.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST fjf464c.pas: ./test_run: line 199: 13383 Segmentation fault ./"$A_OUT" "$x" TEST fjf464e.pas: ./test_run: line 199: 13441 Segmentation fault ./"$A_OUT" "$x" TEST fjf480a.pas: SKIPPED: librx not installed TEST fjf480b.pas: SKIPPED: librx not installed TEST fjf480c.pas: SKIPPED: librx not installed TEST fjf558m.pas: O./test_run: line 199: 23669 Bus error ./"$A_OUT" "$x" TEST fjf558n.pas: O./test_run: line 199: 23691 Bus error ./"$A_OUT" "$x" TEST fjf56.pas: SKIPPED: only for IA32 TEST fjf582.pas: ./test_run: line 199: 26315 Segmentation fault ./"$A_OUT" "$x" TEST fjf664.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST fjf77.pas: SKIPPED: range of LongReal not sufficient for test TEST fjf92.pas: SKIPPED: only for IA32 TEST fproc.pas: 4c4,11 < ./test_run: line 188: 5375 Segmentation fault ./"$A_OUT" "$x" --- > Stack frame: 0 formal print = 4 formal routine = 4 > Stack frame: 1 formal print = 4 formal routine = 4 > Stack frame: 2 formal print = 4 formal routine = 4 > Stack frame: 3 formal print = 4 formal routine = 4 > Stack frame: 4 formal print = non-local jump > Stack frame: 8 formal print = -1 formal routine = -1 > Stack frame: 9 formal print = -1 formal routine = -1 > Stack frame: 10 formal print = -1 formal routine = -1 failed TEST gettexttest.pas: SKIPPED: libintl not installed TEST gmptest.pas: SKIPPED: libgmp not installed TEST goto4.pas: O./test_run: line 199: 5666 Bus error ./"$A_OUT" "$x" TEST goto5.pas: O./test_run: line 199: 5688 Bus error ./"$A_OUT" "$x" TEST heapmo2.pas: OK ./test_run: line 199: 6054 Bus error ./"$A_OUT" "$x" TEST heapmontest.pas: OK ./test_run: line 199: 6086 Segmentation fault ./"$A_OUT" "$x" TEST jj5.pas: SKIPPED: `attribute (stdcall)' not available TEST knuth1.pas: ./test_run: line 199: 7349 Segmentation fault ./"$A_OUT" "$x" TEST longr2.pas: SKIPPED: no LongReal math routines available TEST math.pas: 2d1 < ./test_run: line 188: 8385 Segmentation fault ./"$A_OUT" "$x" failed TEST nlgpp.pas: ./test_run: line 199: 10696 Segmentation fault ./"$A_OUT" "$x" TEST nlgpp2.pas: 2c2,30 < ./test_run: line 188: 10718 Segmentation fault ./"$A_OUT" "$x" --- > Recursive start 10 True > Recursive start 9 True > Recursive start 8 True > Recursive start 7 True > Recursive start 6 True > Recursive start 5 True > Recursive start 4 True > Recursive start 3 True > Recursive start 2 False > Recursive start 1 False > Recursive start 0 False > DoGoto 3 True > OK > Recursive end 3 True > Recursive before goto 4 True > Recursive end 4 True > Recursive before goto 5 True > Recursive end 5 True > Recursive before goto 6 True > Recursive end 6 True > Recursive before goto 7 True > Recursive end 7 True > Recursive before goto 8 True > Recursive end 8 True > Recursive before goto 9 True > Recursive end 9 True > Recursive before goto 10 True > Recursive end 10 True > Main end failed TEST nonlocgoto.pas: 3c3 < ./test_run: line 188: 10852 Bus error ./"$A_OUT" "$x" --- > it worked failed TEST readb1.pas: ./test_run: line 199: 12272 Segmentation fault ./"$A_OUT" "$x" TEST readb10.pas: ./test_run: line 199: 12299 Segmentation fault ./"$A_OUT" "$x" TEST readb11.pas: ./test_run: line 199: 12326 Segmentation fault ./"$A_OUT" "$x" TEST readb12.pas: ./test_run: line 199: 12353 Segmentation fault ./"$A_OUT" "$x" TEST readb13.pas: ./test_run: line 199: 12380 Segmentation fault ./"$A_OUT" "$x" TEST readb2.pas: ./test_run: line 199: 12482 Segmentation fault ./"$A_OUT" "$x" TEST readb3.pas: ./test_run: line 199: 12509 Segmentation fault ./"$A_OUT" "$x" TEST readb4.pas: ./test_run: line 199: 12536 Segmentation fault ./"$A_OUT" "$x" TEST readb5.pas: ./test_run: line 199: 12563 Segmentation fault ./"$A_OUT" "$x" TEST readb6.pas: ./test_run: line 199: 12590 Segmentation fault ./"$A_OUT" "$x" TEST readb7.pas: ./test_run: line 199: 12617 Segmentation fault ./"$A_OUT" "$x" TEST readb8.pas: ./test_run: line 199: 12644 Segmentation fault ./"$A_OUT" "$x" TEST readb9.pas: ./test_run: line 199: 12671 Segmentation fault ./"$A_OUT" "$x" TEST reade1.pas: ./test_run: line 199: 13098 Segmentation fault ./"$A_OUT" "$x" TEST reade10.pas: ./test_run: line 199: 13125 Segmentation fault ./"$A_OUT" "$x" TEST reade11.pas: ./test_run: line 199: 13153 Segmentation fault ./"$A_OUT" "$x" TEST reade12.pas: ./test_run: line 199: 13181 Segmentation fault ./"$A_OUT" "$x" TEST reade13.pas: ./test_run: line 199: 13208 Segmentation fault ./"$A_OUT" "$x" TEST reade15.pas: ./test_run: line 199: 13260 Segmentation fault ./"$A_OUT" "$x" TEST reade2.pas: ./test_run: line 199: 13312 Segmentation fault ./"$A_OUT" "$x" TEST reade3.pas: ./test_run: line 199: 13339 Segmentation fault ./"$A_OUT" "$x" TEST reade4.pas: ./test_run: line 199: 13366 Segmentation fault ./"$A_OUT" "$x" TEST reade5.pas: ./test_run: line 199: 13393 Segmentation fault ./"$A_OUT" "$x" TEST reade6.pas: ./test_run: line 199: 13420 Segmentation fault ./"$A_OUT" "$x" TEST reade7.pas: ./test_run: line 199: 13447 Segmentation fault ./"$A_OUT" "$x" TEST reade8.pas: ./test_run: line 199: 13474 Segmentation fault ./"$A_OUT" "$x" TEST reade9.pas: ./test_run: line 199: 13501 Segmentation fault ./"$A_OUT" "$x" TEST readg1.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg10.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg11.pas: ./test_run: line 199: 13572 Segmentation fault ./"$A_OUT" "$x" TEST readg12.pas: ./test_run: line 199: 13599 Segmentation fault ./"$A_OUT" "$x" TEST readg13.pas: ./test_run: line 199: 13626 Segmentation fault ./"$A_OUT" "$x" TEST readg15.pas: ./test_run: line 199: 13678 Segmentation fault ./"$A_OUT" "$x" TEST readg2.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg3.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg4.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg5.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg6.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg7.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg8.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST readg9.pas: gpc: Internal error: Illegal instruction (program gpc1) Please submit a full bug report to <gpc(a)gnu.de>. failed TEST regextest.pas: SKIPPED: librx not installed TEST systemtest.pas: Error in HeapError #2 TEST t6334-2.pas: ./test_run: line 199: 17360 Illegal instruction ./"$A_OUT" "$x" TEST t6p6p3p4.pas: ./test_run: line 199: 17382 Bus error ./"$A_OUT" "$x" TEST trap2test.pas: ./test_run: line 199: 17848 Segmentation fault ./"$A_OUT" "$x" TEST traptest.pas: ./test_run: line 199: 17884 Segmentation fault ./"$A_OUT" "$x" # of GPC tests 2857 # of GPC tests passed 2772 # of GPC tests skipped 18 # of GPC tests failed 67

2 14

Standard question: Exporting of predefined identifiers
by Frank Heckenbach 01 Feb '03

01 Feb '03

Does EP allow a module to export a predefined identifier? The standard makes it clear that it can re-export an identifier imported from another module (e.g., 6.11.6, example 2), but what about predefined things? As in my other mail, I can't seem to find a wording that prohibits it (but I might overlook something). In particular, exporting "magic" routines with renaming would seem quite confusing to me. module m interface; export m = (WriteLn => Foo); end. program p; import m; begin Foo (1 : 2) { Nice!? } end. If this is allowed, the problem in the `System' unit with the redeclaration of `Integer' could be resolved by letting the `GPC' module export `Integer' with renaming, so `System' could use the renamed one on the right side of the redeclaration (`type Integer = OriginalInteger (16);'). But somehow I doubt this is alright ... Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707

2 4

SizeOf packed record is different when record placed into packed array [0..0], see source please
by Ingvar Marny 31 Jan '03

31 Jan '03

Hi All. program test; type t1 = packed record item1 : byte; item2: byte; item3: byte; end; t2 = packed array [0..0] of t1; begin writeln ('SizeOf (t1): ', SizeOf (t1)); writeln ('SizeOf (t2): ', SizeOf (t2)); readln; end. Output of program: SizeOf (t1): 3 SizeOf (t2): 4 Could anybody tell me - why? Thanks. software: gpc version 2.1 (20020510), based on 2.95.3 20010315 (release) Linux RedHat 2.5.52

3 2

Standard question: Nested functions with the same name
by Frank Heckenbach 31 Jan '03

31 Jan '03

Consider the following situation: program Foo; function a: Integer; function a: Integer; begin a := 42 end; begin a := a end; begin WriteLn ('OK') end. The problem here is that within the outer `a', the identifier `a' can mean both its result variable and the local function `a'. BP allows the declaration, but not the assignment `a := a' (because apparently interprets `a' to mean the local `a'), so there seems to be no way to return a meaningful value from the outer `a' which would render the function quite useless. In EP I don't seem to find any wording that forbids it (but it's quite confusing as usual, so I might have missed it). GPC currently doesn't allow the declaration of the inner `a'. This seems reasonable to me, but is it conforming with the standard? Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707

2 3

Can you make libgpc.a a shared lib?
by Richard D. Jackson 31 Jan '03

31 Jan '03

Is it possible to make libgpc.a a shared lib? If so how do I go about it? If not why not? I didn't find a answer in the doc's so I'm asking here. Thanks Richard

5 24

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc January 2003