Welcome, Guest.
Please login or register.
Search Results - Recent posts as of less than a minute ago
Forum Login
Login Name: Create a new account
Password:     Forgot password

Search Results - Recent posts as of less than a minute ago
10 Pages 1 2 3 4 5 6 7 8 9 10 ... »
Showing 1 - 30 (273 results found)

Re: xblite.exe revision 2.41.16 Posted by: gentsky
Date Posted: June 27, 2017, 9:20pm
Word-Hits
1 (100.00%)
Hi Guy,

I am building a new dll which contains a lot of assembly language so decided to use your release 16 and take advantage of your CODE, END CODE facility. It is very useful and is working well but I did spot a few minor anomalies when setting up sections. They are not serious but I have created a small test script to demonstrate them and have attached it here for your consideration.

Regards,

Alan


Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 27, 2017, 8:25pm
Word-Hits
1 (100.00%)
The new and improved Xblite compiler xst.x

Please find attached: xst_71_26jun17_src.zip (revision 71 - 27 June 2017), which contains:
1.xst.x
2.xbl.def (for the new functions)
3.makexst.mak
4.BuildXstDll_bat.txt (to be renamed BuildXsxDll.bat)

(xblite 2.41.16 3 of 5)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 27, 2017, 8:16pm
Word-Hits
1 (100.00%)
The new and improved Xblite compiler xsx.x

Please find attached: xsx_23_26jun17_src.zip (revision 23 - 27 June 2017), which contains:
1.xsx.x
2.xst.dec (for the new intrinsic types)
3.makexsx.mak
4.BuildXsxDll_bat.txt (to be renamed BuildXsxDll.bat)

(xblite 2.41.16 2 of 5)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 27, 2017, 8:04pm
Word-Hits
1 (100.00%)
27 June 2017
Hi Xbliters,

Please find attached xblite_2_41_16_src.zip, which contains:
- xblite.x: source of the Xblite compiler
- BuildXbiteExe_bat.txt to compile it (rename it first BuildXbiteExe.bat)
- makexblite.mak: the make file used by BuildXbiteExe.bat
- xst.dec: contains the new types
'
' r71-new+++
  $$ASCII               = 19 ' Ansi WinAPIs
  $$UTF8                = 20 ' UTF 8 bit encoding
  $$UTF16_LE            = 21 ' Little Endian 16-bit encoding (Windows)
  $$WIDE                = 21 ' Unicode WinAPIs
  $$UTF16_BE            = 22 ' Big Endian 16-bit encoding (Internet)
  $$UTF32_LE            = 23 ' 32-bit Intel machines
  $$UTF32_BE            = 24 ' Big Endian 32-bit encoding (Motorola, ...)
' r71-new~~~
'
' r71-new+++
' Explicit Integers (imported data record)
'
$$INT8                =  2 ' == $$SBYTE : 8-bit integer
$$UINT8               =  3 ' == $$UBYTE : unsigned 8-bit integer
$$INT16LE             =  4 ' == $$SSHORT: Little Endian 16-bit integer (Windows)
$$UINT16LE            =  5 ' == $$USHORT: Little Endian unsigned 16-bit integer (Windows)
$$INT32LE             =  6 ' == $$SLONG : Little Endian 32-bit integer (Windows)
$$UINT32LE            =  7 ' == $$ULONG : Little Endian unsigned 32-bit integer (Windows)
$$INT64LE             = 12 ' == $$GIANT : Little Endian 64-bit integer (Windows)
' r71-new~~~
'
' r71-new+++
' Byte Order Marks (borrowed from Alan Gents' unc.x)
'
'
     $$BOM8$          = "\xEF\xBB\xBF" ' UTF-8
     $$BOM16$         = "\xFF\xFE" ' Normal   16 bit BOM - LE machine stores as FFFE - BE machine stores as FEFF
     $$INVERSE_BOM16$ = "\xFE\xFF" ' Inverted 16 bit BOM - used to emulate BE output on LE machine
     $$BOM32$         = "\xFF\xFE\x00\x00" ' Normal   32 bit BOM - LE machine stores as FFFE0000 - BE machine stores as 0000FEFF
     $$INVERSE_BOM32$ = "\x00\x00\xFE\xFF" ' Inverted 32 bit BOM - used to emulate BE output on LE machine
' r71-new~~~
'
Enjoy!
Bye! Guy

PS. For Alan Gent.
I believe that there was a problem in your unc.x; correct is:
     $$BOM8          = 0xEFBBBF ' UTF-8
     $$BOM16         = 0xFFFE ' Normal   16 bit BOM - LE machine stores as FFFE - BE machine stores as FEFF
     $$INVERSE_BOM16 = 0xFEFF ' Inverted 16 bit BOM - used to emulate BE output on LE machine
     $$BOM32         = 0xFFFE0000 ' Normal   32 bit BOM - LE machine stores as FFFE0000 - BE machine stores as 0000FE

(xblite 2.41.16 1 of 5)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 26, 2017, 4:09am
Word-Hits
1 (100.00%)
My new and improved personal Grab Bag.

Please find attached: grab_bag_26jun17_src.zip (26 June 2017), which contains:
1.accessors and stringaccessors(from Callum Lowcay)
2.QuickSort (to rebuild xsx.x)
3.Wapi (Windows APIs for Xsed)
4.XGrid (an Xblite wrapper for the grid custom control)

This is my personal touch

(xblite 2.41.16 5 of 5 - the end!)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 26, 2017, 3:58am
Word-Hits
1 (100.00%)
The new and improved XFORMAT.x

Please find attached: xformat_3_26jun17_src.zip (revision 3 - 26 June 2017), which contains:
1.XFORMAT.x
2.makexformat.mak
3.BuildXformatDll_bat.txt (to be renamed BuildXformatDll.bat)

(xblite 2.41.16 4 of 5)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: June 26, 2017, 3:52am
Word-Hits
1 (100.00%)
The new and improved Xblite standard library xst.x

Please find attached: xst_23_26jun17_src.zip (revision 23 - 26 June 2017), which contains:
1.xst.x
2.xst.dec (for the new intrinsic types)
3.makexst.mak
4.BuildXstDll_bat.txt (to be renamed BuildXstDll.bat)

(xblite 2.41.16 3 of 5)

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 30, 2017, 7:22pm
Word-Hits
1 (100.00%)
Hi Alan.

Done and uploaded!

Bye! Guy

Re: xblite.exe revision 2.41.16 Posted by: gentsky
Date Posted: May 29, 2017, 9:19pm
Word-Hits
1 (100.00%)
Hi Guy,

Xblite_1209.x looks OK to me.

You might want to tidy up the comments:
The original comment "with nothing at ebp - 20" should be changed to "with nothing at ebp - 36" on the NEW line only

Cheers,

Alan

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 29, 2017, 4:51pm
Word-Hits
1 (100.00%)
Hi Alan.

Please find attached a corrected version of xblite.x.
Could you please check if I got your fix right?
Kindly drop me a note to confirm or contest.

Bye! Guy

PS.
I added the following header comments:
Line 370
' - gentsky discovered a minor problem where 4 too many zeros are pushed on to the stack
'   when initializing locals in a function.
'   This problem is totally harmless and extremely easy to fix merely requiring -24 to be
'   changed to -40 at the point where the number of dwords is calculated.
' r16-new~~~

And the following code:
Line 6106
' gentsky-28may17-fix:
' The number of DWORDS was and still is calculated as:          count     = ((-24 - zeroz) >>> 2) + 1
' It should now be changed to:                                  count     = ((-40 - zeroz) >>> 2) + 1
' I have made this change in my current xblite and all cases below now push the correct number of zeros
' This problem is completely benign but wastes clock cycles and slows down any function with 1 or more locals
' gentsky---
'          count     = ((-24 - zeroz) >>> 2) + 1                                                            ' with nothing at ebp-20
          count     = ((-40 - zeroz) >>> 2) + 1                                                            ' with nothing at ebp-20
' gentsky~~~

Re: xblite.exe revision 2.41.16 Posted by: gentsky
Date Posted: May 28, 2017, 9:06am
Word-Hits
1 (100.00%)
Hi Guy,

Attached is a small test program regarding the minor problem where 4 too many zeros are pushed on to the stack when initializing locals in a function. This problem is totally harmless and extremely easy to fix merely requiring -24 to be changed to -40 at the point where the number of dwords is calculated. More explanation is given in the comments within locals_8799.x

I did try posting this some days ago but it just disappeared! Hopefully we'll have better luck this time.

Cheers,

Alan

Re: xblite.exe revision 2.41.16 Posted by: gentsky
Date Posted: May 19, 2017, 7:36pm
Word-Hits
1 (100.00%)
Hi Guy,

Thanks for you response. I think reverting to the 3 instruction prologue instead of ENTER is the best idea.

If you are having space problems with GoAsm I have a couple of suggestions:

1. The version of GoAsm in the current Xblite distribution is very out of date. You could try downloading the latest version from the GoDevTools site and see if it can cope with larger files.

2. If not, could you split your 1 large file into 2 or more smaller ones. Try splitting off a lot of the smaller support functions into a separate .lib or .dll

Cheers,

Alan

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 18, 2017, 1:48am
Word-Hits
1 (100.00%)
May 17, 2017

Hi Xbliters!

Please find attached XstLog_XstLogGMT.zip, which contains the modified source xsed.x of xsed.exe Revision 1.33.
- The XstLog function.doc
- The XstLogGMT function.doc

Time in log file are by default local time. I added the XstLogGMT function in Xst.x in order to use GMT time.

Please find attached XstLog_XstLogGMT.zip: description of XstLog and XstLogGMT in the style of Xblite manual in attached XstLog_XstLogGMT.zip.

They are .doc, described by MS Word as "Document Word 97-2003".

Could it please, be merged to the Xblite manual: xblite_manual.chm?

Bye!
Guy

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 18, 2017, 1:43am
Word-Hits
1 (100.00%)
May 17, 2017

Hi Xbliters!

Please find attached xsed_v2_41_16.zip, which contains the modified source xsed.x of xsed.exe Revision 1.33.
- xsed.x
- the custom makexsed.mak
- CompileXsed_bat.txt (to rename CompileXsed.bat)
- a GRAB directory .\xsed\wapi\
- ...

As a matter of safety, CompileXsed.bat will backup your c:\xsed files in directory .\bak\.

Bye!
Guy

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 18, 2017, 1:35am
Word-Hits
1 (100.00%)
May 17, 2017

Hi Xbliters!

Please find attached xblib_v2_41_16.zip, which contains all the modified sources of XFORMAT.dll Revision 3:
- XFORMAT.x
- the custom makexformat.mak
- BuildXformatLib_bat.txt (to rename BuildXformatLib.bat)

Bye!
Guy

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 18, 2017, 1:30am
Word-Hits
1 (100.00%)
May 17, 2017

Hi Xbliters!

Please find attached xsx_v2_41_16.zip, which contains all the modified sources of Xsx.dll Revision 23:
- the new xst.h
- xsx.x
- the custom makexsx.mak
- BuildXsxDll_bat.txt (to rename BuildXsxDll.bat)
- a backup directory .\bak\

As a matter of safety, BuildXsxDll.bat will backup your c:\xblite files in directory .\old\, which is created "on the fly".

Bye!
Guy

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 17, 2017, 11:21pm
Word-Hits
1 (100.00%)
Hi Alan,

Thank you so much for your time reviewing my changes: I have a tendency to go one step too many, so I appreciate that you had taken the time to pinpoint my oversight.

I implemented the 'enter' opcode because I exceeded a size limit compiling my program vxbl.x. I found this way to cut the generated GoAsm source down in a safe manner. And I figured:
"If Intel knows of this problem since back to the '80s, they might have speed up their microcode in three decades".

So, since I'm using the compile flag "-rc" to reduce the size of the source.asm file, I can generate 'enter' opcodes when size counts, and the 3 opcode sequence otherwise.

How do you feel about that?
Probably, I'd better forget about the 'enter' opcode altogether, shouldn't I?

In the mean time, I take in account your comment: I'm reverting back this 'enter' addition and I post here a corrected version ASAP.

Bye!
Guy

Re: xblite.exe revision 2.41.16 Posted by: gentsky
Date Posted: May 17, 2017, 2:11pm
Word-Hits
1 (100.00%)
Hi Guy,

Thanks for all you efforts on the new compiler version - I can see you have been very busy!!
I have only recently come back to Xblite after a long absence and am catching up on things. I have looked through xblite.x to see what you have been changing and note that you are doing a lot of tidying up besides your new CODE, GRAB and  STRIP facilities. One such change involves replacing the standard 3 instruction function entry with ENTER. I wonder if you realize just how very slow this is. I am attaching a small test program which compares the speed of various function entry / exit methods. You will see that ENTER slows things down dramatically.

There is an existing problem with xblite.x which causes the function entry to generate 4 excess pushes when initializing the local variables area. This is nothing to do with your changes but dates back to 2007 when the stack frame was modified to include an unwind space of 16 bytes. Various changes were made as a result of this but one seems to have been missed in the initialization routine. It is a minor correction and I am currently testing the fix on a modified xblite.x . I will post a separate entry / test file for this soon.

Best Wishes,

Alan

P.S. For some reason, my file enter.x has been renamed enter_1653.x when I attached it!

sqlite3 files and examples Posted by: XBLiteAdmin
Date Posted: November 17, 2016, 8:41am
Word-Hits
1 (100.00%)
Attached are the sqlite3 libraries which can be used with xblite. There are also a few example programs using sqlite3 functions to create and manipulate records in a database.

Re: static lib Posted by: XBLiteAdmin
Date Posted: November 15, 2016, 12:35am
Word-Hits
1 (100.00%)
It sounds like you need to make sure all of the xblite environment variables are set correctly.
This will ensure the compiler can find all the required files needed to link to libraries, either static or dynamic ones.
See example below:

Name                           Value
----                           -----
INCLUDE                     G:\xblite\include;G:\xblite\include;include
LIB                            G:\xblite\lib;G:\xblite\lib;lib
M4PATH                      G:\xblite\include;G:\xblite\include;include
XBLDIR                       G:\xblite

To check if the environment variables are correctly set, you can open a Command Prompt console and type SET, or
in Windows 10, from Run, enter Powershell, then type Get-ChildItem Env:

In Windows, to manually change/edit the environment variables, Open Control Panel > System & Security > System > Advanced System Settings and in the System Properties Dialog under Advanced tab, click on Environment Variables. From there you can see the current variables for xblite, which are INCLUDE, LIB, PATH, M4PATH, and XBLDIR.

Re: X SED Posted by: XBLiteAdmin
Date Posted: November 15, 2016, 12:07am
Word-Hits
1 (100.00%)
XSED is written in xblite. The source code is available to download with the xblite source code from the xblite.com website.

http://xblite.com/xblite_241_src.zip

X SED Posted by: teslaXB
Date Posted: October 26, 2016, 10:25pm
Word-Hits
1 (100.00%)
hi
I have question about XSed editor.
i know that is based on SED by jose roca.
Is XSED written in XBlite ?
And if is ..is open source ?
And if is where i can found source code?
thanks!

static lib Posted by: ly47
Date Posted: September 20, 2016, 9:44pm
Word-Hits
1 (100.00%)
Hi
when compiling with static libs : IMPORT "xst_s.lib" IMPORT "xsx_s.lib" (benchmark.x)
Lots of errors.
But when changed to IMPORT "xst" IMPORT "xsx",  compiles fine.
I tried other examples that use static libs ,all the same errors.
Please help
thaks
ly

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: August 13, 2016, 2:08am
Word-Hits
1 (100.00%)
Hi Xbliters,

I corrected a (rare) bug in the handling of GRABbed file paths.
Please, download the attached version of xblite.x, with the proper xst.dec that contains additional constants, such as $$ASCII, $$UTF16_LE...

Bye! Guy

Re: XBLite Release 17 Posted by: Guy1954
Date Posted: June 12, 2016, 7:59pm
Word-Hits
1 (100.00%)
Hi Xbliter.

I spend a whole week testing the GRAB and CODE statements.
I threw as many curveballs as I could think of, and they were to no avail.

Please find attached my latest version of XBLite compiler revision 16.

Bye! Guy

Re: XBLite Release 17 Posted by: Guy1954
Date Posted: June 8, 2016, 9:26pm
Word-Hits
1 (100.00%)
Hi Xbliter,

I succeeded to break the new GRAB directive!
The patch to correct the bug was just an IF condition change.

I uploaded the corrected xblite.x, so that you can get a chance to catch another corner case.

Bye! Guy

Re: XBLite Release 17 Posted by: Guy1954
Date Posted: June 5, 2016, 4:16pm
Word-Hits
1 (100.00%)
Hi Xbliters,

This is ASCII xblite compiler with 2 additional features:
1. CODE and END CODE, which injects assembler code by bulk-prependding with the keyword ASM
  CODE and END CODE are 2 new XBLite keywords (and therefore recognized by the XBLite compiler)

2.GRAB "file_to_grab", which is an IMPORT statement at pre-compilation time
  GRAB is _not_ a new XBLite keyword but a pre-processing directive.

Note that GRABbing an assembler source file will insert the assembler source between a pair of (CODE, END CODE) for proper compilation.

Bye! Guy

Re: xblite.exe revision 2.41.16 Posted by: Guy1954
Date Posted: May 2, 2016, 11:48am
Word-Hits
1 (100.00%)
Dear Xbliters,

The compiler xblite version 2.41 revision 16 must be installed
in order to compile revision 17, which handles Unicode.


However, revision 16 offers new possibilities for GoAsm code
injection; as a for instance, here is how I emulated (for fun) the
standard function XstCopyMemory (sourceAddr, &dest$, bytes) in
xblite.x revision 17 (compilable with revision 16):

               ' r17-XstCopyMemory (sourceAddr, &dest$, bytes)

'#################################################################
' r17-assume a 32 bit processor
CODE
     mov     ecx,[EmitString.bytes]      ; byte count
     jecxz > .is_zero32_end              ; LEN(source$) == 0

     mov     esi,[EmitString.sourceAddr] ; source string
     mov     edi,[EmitString.dest$]      ; destination string

     shr     ecx,2
     jecxz > .is_zero32_01     ; LEN(source$) <= 3
     cld
     rep movsd                    ; 32-word shuffle

.is_zero32_01
     mov     ecx,[EmitString.bytes]
     and     ecx,3
     jecxz > .is_zero32_end
     cld
     rep movsb                    ; the very last bytes

.is_zero32_end
END CODE
'#################################################################

I believe that Coders such as bushpilot and gentski will
appreciate the convenience of this CODE statement, drawn
from my needs as an assembler Noob.

The GRAB statement was also great help in xsx.x in order to
generate "typed" quick sort routines from a single "grabbed"
snippet.

However, I would appreciate if you put it to the test as I can't
cover all the regressions, in spite of my heavy duty testing.

Happy xbliting!
Bye! Guy

Re: Creating .dec Posted by: XBLiteAdmin
Date Posted: March 2, 2016, 11:31pm
Word-Hits
1 (100.00%)
Hi Peters,

Did the DLL come with any library or header files (perhaps C files?). You need to match the correct TYPE definitions for variables in the DLL functions. Otherwise, data is not aligned correctly. You may want to post the .dec file you created.

David

Re: Creating .dec Posted by: Peters
Date Posted: January 12, 2016, 10:22pm
Word-Hits
1 (100.00%)
I have managed to create .dec file by following other threads.
All seemed to be working ok, until some off my numeric variables were going completely haywire.
I remembered this happening last time, and again someone gave me a fix. PLEASE PLEASE help me as I have no idea what to do to resolve it.
Peters

10 Pages 1 2 3 4 5 6 7 8 9 10 ... »
Showing 1 - 30 (273 results found)