Re: [flac-dev] How to check for 64-bit CPU?

2015-12-30 Thread Thomas Zander
On 29 December 2015 at 08:08, Erik de Castro Lopo wrote: > I would suggest: > >#if SIZEOF_VOIDP == 8 I believe this is not portable. At least on my machine ("4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") it's not defined. Probably this one comes closest: #define

Re: [flac-dev] FLAC__BYTES_PER_WORD==8 test results

2015-12-30 Thread Thomas Zander
On 29 December 2015 at 21:50, lvqcl wrote: > So, does it make sense to #define FLAC__BYTES_PER_WORD (in bitreader.c) > as 4 for 32-bit and as 8 for 64-bit targets? Your tests so far imply this is a sensible default. I'd say go ahead. We can always change it if it turns out there is a better opti

Re: [flac-dev] How to check for 64-bit CPU?

2015-12-30 Thread LRN
On 30.12.2015 13:57, Thomas Zander wrote: > On 29 December 2015 at 08:08, Erik de Castro Lopo wrote: > >> I would suggest: >> >>#if SIZEOF_VOIDP == 8 > > I believe this is not portable. At least on my machine ("4.2.1 > Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") > it'

[flac-dev] FLAC Application ID's

2015-12-30 Thread Matthew Foust
We would like to reserve several FLAC Application ID's: App Name: Myriad App ID: "AFMY" / 41454d59 URL: http://www.audiofile-engineering.com/myriad App Name: Triumph App ID: "AETR" / 41455452 URL: http://www.audiofile-engineering.com/triumph App Name: Fidelia App ID: "AETW" / 41455457 URL: http:

[flac-dev] About flac id page

2015-12-30 Thread lvqcl
There are several (dead?) projects with dead links on xiph.org/flac/id.html page: FlacFile, Bugs Player, MOTB MetaCzar(?), Parseable Embedded Extensible Metadata. The content of these websites can become unpredictable... Maybe it makes sense to remove hyperlinks to 3rd-party websites from this pa

Re: [flac-dev] FLAC Application ID's

2015-12-30 Thread lvqcl
Matthew Foust wrote: > App ID: "AFMY" / 41454d59 You mean "AEMY" ? > Would you please clarify for me what the specification URL is? IMHO it's simply an address of a web page that contains the specification for your custom metadata block. The specification means: its purpose, how to parse it,

Re: [flac-dev] FLAC Application ID's

2015-12-30 Thread Matthew Foust
Correct, AEMY. Nice catch. Thanks for the explanation of the spec URL! Matthew Foust Audiofile Engineering http://www.audiofile-engineering.com > On 2015-12-30 , at 11:42, lvqcl wrote: > > Matthew Foust wrote: > >> App ID: "AFMY" / 41454d59 > > You mean "AEMY" ? > > >> Would you please cl

Re: [flac-dev] How to check for 64-bit CPU?

2015-12-30 Thread Erik de Castro Lopo
Thomas Zander wrote: > I believe this is not portable. At least on my machine ("4.2.1 > Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") Its *is* detected and defined by autoconf at configure time. Erik -- -

Re: [flac-dev] How to check for 64-bit CPU?

2015-12-30 Thread Erik de Castro Lopo
LRN wrote: > Guys, you do know that there are canned, portable autoconf macros for > checking things like variable sizes at configuration/compilation time, right? Indeed! Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/

Re: [flac-dev] How to check for 64-bit CPU?

2015-12-30 Thread Brian Willoughby
It seems that most compilers define some sort of architecture values, but they're not necessarily consistent across all compilers. I believe that the original point of the FLAC__CPU_X86_64 and similar defines was to make these consistent within the FLAC sources, but not to reinvent the wheel ent

Re: [flac-dev] FLAC__BYTES_PER_WORD==8 test results

2015-12-30 Thread Brian Willoughby
On Dec 30, 2015, at 3:09 AM, Thomas Zander wrote: > On 29 December 2015 at 21:50, lvqcl wrote: >> So, does it make sense to #define FLAC__BYTES_PER_WORD (in bitreader.c) >> as 4 for 32-bit and as 8 for 64-bit targets? > > Your tests so far imply this is a sensible default. > I'd say go ahead.