Closed
Bug 851424
Opened 13 years ago
Closed 13 years ago
make 64-bit+32-bit versions of ff, tb, etc available
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jmichae3, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130307023931
Steps to reproduce:
want to use firefox on 64-bit machine natively
Actual results:
I get a 32-bit product (to my knowledge)
Expected results:
the installer should provide the either both or the correct kind of executables.
mingw-w64 (gcc) gives me 64-bit and 32-bit executables (separate compilers for each).
what I usually do is make a 32\ and 64\ directory and for windows I make shortcuts to the 64-bit exe and make the working directory the 64\ or 32\ so it sees the appropriate DLLs in that dir. i believe they also have compilers for linux too.
voila, you now have 32+64-bit ff, tb, etc. and I think this same method is portable to linux and not sure about mac - someone knowledgeable about mac would have to answer on that.
mingw-w64 you have to stay on the mailing list and prod once in a while when compiler landscape changes to see what's viable. right now rubenvb's compilers are the thing to get. they need donations and work to have buildbot working again for windows. so for now, only the personal builds are kept up to date.
these builds work for auto builds (32-bit and 64-bit target, windows):
mingw-w32-bin_i686-mingw_20110812
mingw-w32-bin_i686-mingw_20111127
mingw-w32-bin_i686-mingw_20111209
mingw-w32-bin_i686-mingw_20111210
mingw-w32-bin_i686-mingw_20111212
mingw-w32-bin_i686-mingw_20111214
mingw-w64-bin_i686-mingw_20110827
mingw-w64-bin_i686-mingw_20111127
mingw-w64-bin_i686-mingw_20111220
| Reporter | ||
Comment 1•13 years ago
|
||
| Reporter | ||
Comment 2•13 years ago
|
||
oops, rubenvb's files are at:
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/
auto builds are at
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Automated%20Builds/
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/
project files are at http://sf.net/projects/mingw-w64/files
The windows 64bit builds isn't supported at all anymore.
https://groups.google.com/forum/#!topic/mozilla.dev.apps.firefox/DOihL2429NM
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Comment 4•13 years ago
|
||
windows 9 will be 64-bit only.
| Reporter | ||
Comment 5•13 years ago
|
||
cancel that last comment. :-/ it turns out the article I read from the msdn blogs was written April 1 2008. I dislike being lied to. the truth is much better. makes things so much less complicated.
| Reporter | ||
Comment 6•13 years ago
|
||
I would still like to see 64-bit machine support. I usually have a LOT of tabs open as part of my development environment.
and the browser I run needs to be able to handle it. does this make sense?
this is where you start creeping into the 64-bit realm.
64-bit really should be made available.
what's the real stoppage here? lack of 64-bit test & build computers? lack of compiler? rack space? hosting costs?
or do the developers just not yet know how to do 64-bit development? hey - I am going to be learning a few more things myself soon once I can get a 64-bit box in the house.
one of the things that changes is native pointer size, from 32 bits to 64 bits.
the other thing in c/c++ is the automatic #define _WIN64 only when the 64-bit compiler is used. see
http://jesusnjim.com/programming/common-compiler-defines.html
when I develop code, I try to target for
- 32-bit msdos i386
- 32-bit windows i386
- 64-bit windows x86_64
I can't always do msdos, but I at least try to do 32+64-bit windows.
| Reporter | ||
Comment 7•13 years ago
|
||
I say "creeping into 64-bit realm" because I have run into crashes due to out of memory situations on my 32-bit system, although lately I have not been seeing this problem - but I do not want the possibility again.
if you have ever put a lot of work into making tabs with history on each, and then suddenly lost them all due to lack of memory, you get gun shy a little.
| Reporter | ||
Comment 8•13 years ago
|
||
I am having problems with the 32-bit 4GiB limit on my 64-bit windows 7 system that has 64GiB of RAM.
please make a version of the browser that installs the appropriate 32 or 64-bit version of the browser on the machine. thanks.
right now, when I look at firefox.exe in taskmgr, I see firefox.exe *32
| Reporter | ||
Comment 9•12 years ago
|
||
if a 64-bit version is not being provided, I can give several reasons to do so:
- everything is 64-bit now and will stay that way for quite a while I should think. only a very few machines are 32-bit and those are considered legacy.
- you will nave the 3rd 64-bit popular browser besides IE and waterfox.
- less crashes due to memory usage
please provide a 64-bit version. TB and FF both need it. I frequently work with my ff browser having 70+ tabs. and lots of people have very large inboxes, which will still be a problem even though there is now supposed to be support for 64-bit filesystems in tb, due to the amount of memory the indexes take up - it fills up the available memory that 4GiB limit 32-bit apps are stuck with.
choice of a different compiler set that provides 32+64-bit target support, conversion of the code base to the new compiler set may be necessary to bring the code base into the 21st century. I think it would be worth the effort. instead of coming out with fixes every 6 months, etc. reduce the release frequency so devs and focus on code conversion and maybe even announce a 64-bit version when the time comes.
You need to log in
before you can comment on or make changes to this bug.
Description
•