similar to: Token.c appears to have a bug.

I am still chasing this down, but in doing the build for OpenVMS, I have discovered that one of the popt modules is using HAVE_ALLOCA_H to determine if the alloca function is on a platform. That is not a good assumption. Compaq C does have an alloca() built in (slightly different symbol name, I assume because of symbol naming rules in the C standard.) Because alloca is a non-standard

The Open Group Single Unix standard shows that the data types int64 and uint64 are defined in the inttypes.h header file. Rsync is not including this file, nor is there a feature test for this header file in the configure phase, but rsync is using these data types. -John wb8tyw@qsl.net Personal Opinion Only

Compaq C 6.5 OpenVMS Alpha 7.3 The config.h.in template file is missing the line: #undef HAVE_INET_NTOP This caused the resulting CONFIG.H on OpenVMS to not test for the existance of the inet_ntop() routine in it's system tables. This configure bug exposed that the prototype in inet_ntop() in RSYNC.H does not match the one in the Compaq C header files. This stopped the build. I am

What is the status of rsync on Windows 2000? I was looking to install it on my test system, and the download directory has a readme file that says I need the cygnus gnu-win32 library. The link refers me to the index page for cygnus, with no way to get to a download area. A google search shows many mirrors of the download directory. All I have checked are completely blank. I will confess

The parts of klibc specific to the alpha architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 5e5ce29210ac33a0b3704eb9ab5e5d5b55375575 tree 2ec24df596e13c21b68da4d905f546770d36fdad parent 8529b52550ba78984998d3a9cc9deb467217fa3e author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:14 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Hi, all: Now I'm working on writing a backend for Moto MCore, but I don't know how to describe some instructions. First, I've already written MCoreRegisterInfo.td like these: class MCoreReg<bits<4> num, string name> : Register<name> { let Namespace = "MCore"; field bits<4> Num = num; } def R0 : MCoreReg< 0, "R0">,

I am trying to debug the RSYNC client and server by single stepping through them. The server seems to ok up to the point where it is waiting for the client connection. On the client side, I am having trouble finding the right options so that it will connect up to the local server with out fork() a copy of itself or trying to exec the rsh command. This is on RSYNC 2.5.5 on OpenVMS Alpha. If

Hello! This is Kernel 2.4.6-ac1 with ext3-0.8.0 compiled with cvs-gcc version 3.1 20010616 on alpha ev4. I have prepared one ext3 filesystem to play with. When my rc-scripts call mount -a during boot I receive this: Jul 6 22:01:30 Marvin kernel: Bad unaligned kernel access at fffffc0000883f54: fffffc00063f2e6e 2a 2 and the mount of this filesystem fails. A subsequent manual second try to

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are

The tests in rsync for features have been changed to testing the value of a macro definition instead of previously testing if the macro was defined. This testing is now inconsistent with the HAVE_SOCKETPAIR macro, where in some places it is tested to see if the macro is defined, and other places to if it has a non zero value. I would rather not globally disable the diagnostic about undefined

Hello, rsync.h is always including the syslog.h file, even though it is only used when the LOG_DAEMON macro is defined. Could someone change it to be as follows: #ifdef LOG_DAEMON #include <syslog.h> #endif OpenVMS currently does not have a syslog facility, so it does not have a syslog.h. Thank you, -John wb8tyw@qsl.net Personal Opinion Only

Hi, I found that machine dead code elimination, does not respect the calling convention of alpha and eliminates r16, which was set correctly during code generation. I verified it with -print-after-all. Does anybody have a patch for this? On Wed, Jun 29, 2011 at 11:12 AM, Ankit Sethia <asethia at eecs.umich.edu>wrote: > Hi All, > > I am using llvm-2.9 to cross compile to alpha. I

Hi All, I am using llvm-2.9 to cross compile to alpha. I know that alpha is in experimental stage, but i can not get even the "Hello World" program to run on it. Here is what happens, the bitcode file for the hello world program is as follow: ; ModuleID = 'hello.bc' target datalayout =

Re: Per the discussions about spam on this list. Sending a confirming message to an unregistered poster is not a good idea. The return/reply-to addresses in spam is forged, and that is just adding to some victims e-mail. Filtering runs the risk that a legitimate message gets lost, and the sender does not realize it. Filtering is also the most expensive and innefficient way to deal with

Hi, Can people suggest how this is solved for other ISAs? This happens only for Alpha and not for x86-64. The register 16 does not have any uses within that function, but is used inside puts. So Machine DCE thinks it is dead code. On Wed, Jun 29, 2011 at 4:20 PM, Ankit Sethia <asethia at eecs.umich.edu>wrote: > Hi, > > I found that machine dead code elimination, does not respect

Thanks for the comments! Responses below. Teresa On Tue, Jul 21, 2015 at 1:06 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2015-Jul-14, at 13:33, Teresa Johnson <tejohnson at google.com> wrote: > > > > As mentioned in the Updated ThinLTO RFC ( > http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/086211.html), I am > sending the

The G.729.1 "wideband" codec is starting to show a slight bit of traction. There is a possibility that Asterisk could support G.729.1 - would you use it or buy it if it was available? More importantly, does any equipment with which your systems currently exchange traffic support G.729.1? Currently, the number of devices supporting G.729.1 seems to be fairly limited and it

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the HLINK.C module. The cast on function argument for the qsort() routine was wrong, and not allowing the compile to complete. When the function definiton of the hlink_compare() is corrected to have the const qualifiers, the cast inside the qsort() function call is no longer

The following zlib files need patches in order to compile using Compaq C on OpenVMS. These should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) fnmatch.c and mdfour.c. Compaq C on OpenVMS can not deal with relative path names in #include files. Also the local prototype for getenv() does

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the checksum.c module. The type (char) was being used where the usage indicated either (void) or (unsigned char) should be used. The const qualifier was added to impove compiler efficiency. There may be more cases in this module where type (char) is being used instead of what appears