Jump to content



Photo

Request: Native 64bit compile ability


  • Please log in to reply
34 replies to this topic

#21 Valik

Valik

    Former developer.

  • Active Members
  • PipPipPipPipPipPip
  • 18,879 posts

Posted 12 December 2006 - 10:37 PM

I'd like to see the rationale on disabling inline assembly support. That's a very useful feature since it allows mixed-mode programming where the majority of a function is C\C++ and there are a few bits of hand optimized assembly (here's looking at you, DllCall()).





#22 jpm

jpm

    a Real GUI/debug lover

  • Developers
  • 8,925 posts

Posted 13 December 2006 - 12:11 AM

I'd like to see the rationale on disabling inline assembly support. That's a very useful feature since it allows mixed-mode programming where the majority of a function is C\C++ and there are a few bits of hand optimized assembly (here's looking at you, DllCall()).

That's coming from compatibility with compilation for 64-bit Itanium I Think. It can be register access too.

#23 Richard Robertson

Richard Robertson

    Universalist

  • Active Members
  • PipPipPipPipPipPip
  • 9,692 posts

Posted 13 December 2006 - 02:30 AM

Go figure, you need a x64 architecture to call x64 files. Is there no 32bit version you can use?

You need more memory? Isn't 4 GB of data enough? I've never seen anything that would require more than that.

#24 CoePSX

CoePSX

    Polymath

  • Active Members
  • PipPipPipPip
  • 237 posts

Posted 14 December 2006 - 01:33 AM

Isn't 4 GB of data enough?


Perhaps if you want to play a DVD in cached mode then it isn't.

You seem to have a habit of putting things in the wrong place. I feel sorry for any female you attempt to have sex with.


#25 The Kandie Man

The Kandie Man

    All Your Base Are Belong To Us

  • Active Members
  • PipPipPipPipPipPip
  • 950 posts

Posted 16 December 2006 - 09:29 AM

Go figure, you need a x64 architecture to call x64 files. Is there no 32bit version you can use?

You need more memory? Isn't 4 GB of data enough? I've never seen anything that would require more than that.


Example:
Posted Image

Also, for a 64bit OS, you need to load 64bit driver libraries, which you can't load with a 32bit program. Hence a 64bit executable will allow me to load 64bit libraries that deal with the drivers on a system.

An example of this in a very simple manner is the beep function. The autoit Beep() function doesn't work on my 64bit OS. I am not sure why.

There is also a 64bit kernel32.dll (don't bother to ask why, it should be kernel64.dll) which can only be loaded by 64bit applications.

Edited by The Kandie Man, 16 December 2006 - 09:57 AM.

"So man has sown the wind and reaped the world. Perhaps in the next few hours there will no remembrance of the past and no hope for the future that might have been." & _"All the works of man will be consumed in the great fire after which he was created." & _"And if there is a future for man, insensitive as he is, proud and defiant in his pursuit of power, let him resolve to live it lovingly, for he knows well how to do so." & _"Then he may say once more, 'Truly the light is sweet, and what a pleasant thing it is for the eyes to see the sun.'" - The Day the Earth Caught Fire

#26 Guest_Ling_*

Guest_Ling_*
  • Guests

Posted 20 March 2007 - 05:06 PM

Hi,

I am new to AutoIt, and I am looking for tools that can do UI Automation on 64bit WinPE.
What is the current status of this 64bit compile support? Will it be available soon?

Thanks,
Ling

#27 WeMartiansAreFriendly

WeMartiansAreFriendly

    Where's the kaboom?

  • Active Members
  • PipPipPipPipPipPip
  • 1,245 posts

Posted 24 March 2007 - 07:33 PM

most of the newer computers are 64 bit now.. :whistle:
Posted ImageDon't bother, It's inside your monitor!------GUISetOnEvent should behave more like HotKeySet()

#28 Jon

Jon

    Up all night to get lucky

  • Administrators
  • 9,529 posts

Posted 24 March 2007 - 11:09 PM

One of the devs is working on a 64 bit native version. I know this because we get shouted at daily for the bad coding practices we've used that is making it difficult.

#29 Richard Robertson

Richard Robertson

    Universalist

  • Active Members
  • PipPipPipPipPipPip
  • 9,692 posts

Posted 25 March 2007 - 03:52 AM

What are you doing that requires so much memory space and why wouldn't you do it on a very high end computer?

I don't understand portability issues from 32 bit to 64 bit. Is there any easy way to explain them or should I look up a Microsoft knowledge base article?

Edited by Mr Icekirby, 25 March 2007 - 03:55 AM.


#30 Valik

Valik

    Former developer.

  • Active Members
  • PipPipPipPipPipPip
  • 18,879 posts

Posted 25 March 2007 - 04:03 PM

One of the devs is working on a 64 bit native version. I know this because we get shouted at daily for the bad coding practices we've used that is making it difficult.

It's not daily, only the days when I get to work on it which haven't been for a while.

#31 The Kandie Man

The Kandie Man

    All Your Base Are Belong To Us

  • Active Members
  • PipPipPipPipPipPip
  • 950 posts

Posted 31 March 2007 - 01:04 AM

It's not daily, only the days when I get to work on it which haven't been for a while.

O rly? This sounds exciting. Once you guys get all the "bad coding pratices" removed from the 32 bit version, it should be fairly easy to compile it in a 64bit version with practically no modification to the code, except for maybe a few datatypes and other things. No rush, but I am looking forward to the day when I see a x64 subfolder here:
http://www.autoitscript.com/autoit3/files/beta/

The Kandie Man :whistle:
"So man has sown the wind and reaped the world. Perhaps in the next few hours there will no remembrance of the past and no hope for the future that might have been." & _"All the works of man will be consumed in the great fire after which he was created." & _"And if there is a future for man, insensitive as he is, proud and defiant in his pursuit of power, let him resolve to live it lovingly, for he knows well how to do so." & _"Then he may say once more, 'Truly the light is sweet, and what a pleasant thing it is for the eyes to see the sun.'" - The Day the Earth Caught Fire

#32 Jon

Jon

    Up all night to get lucky

  • Administrators
  • 9,529 posts

Posted 31 March 2007 - 10:15 AM

Unfortunately half the Win32 API seems to demand you code in a way that causes a billion warnings - especially under 64bit. I'm not sure how close it is atm - i'll have to check with valik. I know it compiles and runs (did it the other day) but no idea how safe it is. And that was without Pcre support too.

I discovered that AUtoItX didn't work on my windows vista 64bit box the other day (must be some sort of COM restriction) but it worked when compiled in 64bit. So that's fairly important to get working for me too.

#33 Jon

Jon

    Up all night to get lucky

  • Administrators
  • 9,529 posts

Posted 31 March 2007 - 10:24 AM

Well, this explains the AutoitX thing :whistle:

In x64 versions of Windows, a process that starts from a 64-bit executable such as Explorer.exe can only load Win64 DLLs, while a process started from a 32-bit executable can only load Win32 DLLs.



#34 Valik

Valik

    Former developer.

  • Active Members
  • PipPipPipPipPipPip
  • 18,879 posts

Posted 01 April 2007 - 01:28 AM

That's also with DllCall() disabled. It has to be re-written from scratch as well. So it's really not as easy as it appears.

#35 FuryCell

FuryCell

    A cornered fox is more dangerous than a jackal!

  • Active Members
  • PipPipPipPipPipPip
  • 2,437 posts

Posted 08 April 2007 - 10:52 PM

Nice. :shocked: Can't wait to see 64 bit au3 as well. I'm planning to upgrade to 64 bit vista in a couple of months so i will be very glad to see this functional.
HKTunes:Softpedia | GoogleCodeLyricToy:Softpedia | GoogleCodeRCTunes:Softpedia | GoogleCodeMichtaToolsProgrammer n. - An ingenious device that turns caffeine into code.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users