search for: bookkeeping

Our architecture(TCE) can have LOTS of registers. It seems r152019 changed some register bookkeeping data structures to 8-bit. This broke support for architectures with >255 registers. Please revert this change or make those register-related values at least 16 bits wide.

It seems that xenstore watches do not work from domU userspace (they obviously do for drivers). In some preliminary debugging of this, there are two aspects of the failure: not sending the watch to xenstore and not handling watch events for userspace watches. The former can be easily fixed by adding the missing ''case XS_WATCH:'' to xenbus_dev_write() in xenbus_dev.c. The

...paths in the current implementation of PassManager: 1. Pass Y is not re-run because it is considered up-to-date 2. Pass Y is re-run after Pass X because Pass X is out-of-date Which one of these happens? What I'd really like to do is have Pass X re-run but not Pass Y. Pass Y only uses some bookkeeping from Pass X to speed itself up. Having Pass X not re-run could cause Pass Y to give wrong answers, but once Pass X is up-to-date, Pass Y will be fine. Is this at all possible? -Dave

On Mar 5, 2012, at 5:39 AM, Heikki Kultala wrote: > Our architecture(TCE) can have LOTS of registers. > > It seems r152019 changed some register bookkeeping data structures to > 8-bit. This broke support for architectures with >255 registers. > > Please revert this change or make those register-related values at least > 16 bits wide. I agree. We can limit the number of physregs to 64k, but no more. /jakob

...hanges that I have been making are really very minor, all the work is already done. However I can imagine some client side fallout due to the multi-module nature of the proposed solution. The client side problem being that I imagine that many people are using a single monolithic module for various bookkeeping purposes on the client side - function signature lookups for example. One slightly dubious way around this might be to have a monolithic module 'just for bookkeeping' which is managed persistently in 'parallel' to the individual object modules - which I'm currently throwing awa...

...thing ''cos no matter what I do I cannot connect to the database from RoR. I have followed all of the instructions I could find and when I start irb and type "require ''postgres''" I get the value ''true'' echoed back to me. My database is called bookkeeping and has several tables, one of which is called ''address''. I''ve changed the .yml file to have the following: development: adapter: postgresql database: bookkeeping_dev username: toby password: whatever host: localhost schema_search_path: public test: adap...

I am writing a banking / accounting / bookkeeping system for myself. I have orgs (who pay me or who I pay) and line_items (day to day transactions that mirror the entries on my bank statements) On my line_items screen I have a select box with various orgs in it. I''d like to have a way to add an org write there on that screen rat...

Hello all: I have a function that writes a fairly elaborate report based on some survey data. For documentation and bookkeeping purposes, I'd like to write out in the report the function call that produced the report, or at least enough information to help me recreate the steps that led to that report. I've been generating all the reports with scripts, in order to be able to recreate the steps, but apart from the f...

...hen read. But after a new session, all the messages are still "new". Of course, only "baratin" is the owner. The problem, while using mutt and IMAP: mutt refuse to change any flag because the folder is "read only". Of course, this is correct. My question: Why is no bookkeeping maintained for "other" users, although every one has his/her own control and index structure ? Thanks a lot ! Claude

On Mon, Jun 17, 2019 at 07:07:53PM -0500, Eric Blake wrote: > The NBD spec requires that a server doing structured reads must not > succeed unless it covers the entire buffer with reply chunks. In the > general case, this requires a lot of bookkeeping to check whether > offsets were non-overlapping and sufficient, and we'd rather defer > such checking to an optional callback function. But a callback > function will only be reached per chunk, while we still want to fail > the overall read if the callback function was never called...

On Friday 19 September 2008 17:11, David Greene wrote: > What I'd really like to do is have Pass X re-run but not Pass Y. Pass Y > only uses some bookkeeping from Pass X to speed itself up. Having Pass X > not re-run could cause Pass Y to give wrong answers, but once Pass X is > up-to-date, Pass Y will be fine. To make this a bit more concrete: I noticed that the Verifier takes a VERY long time on large programs. This appears to be due to its...

...like this working. I don't know if it's illegal, but this is how libstdc++'s string implementation finds its header data. std::string stores a pointer directly to the character data (making subscripting slightly faster), and then subtracts the size of the header when it needs to do any bookkeeping. Do you have a reference to the standard that makes it undefined?

...= /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes [Apps] comment = Applications path = /apps read only = no public = yes create mask = 1775 directory mask = 1775 [Bookkeeping] comment = Bookkeeping path = /bookkeeping read only = no public = no [archives] comment = Archives path = /archives read only = yes public = yes [Shared] comment = Shared path = /shared read only = no public = yes create mask = 1775 directo...

...;s not obvious from that description, traffic from LAN X travels through through the switch to eth1 on the gateway, where iptables translates it to the IP address of eth0:X and thence out to the net. The gateway is totally idle except for handling these NATs; no other processes except the usual OS bookkeeping. All NIC and switch hardware involved is 100Mb. This all works, but we're experiencing network congestion somewhere. The LANs appear to become saturated when only about 10Mb of total traffic is passing through the public IPs. That is, we seem to be losing almost 90% of our capacity somewhere...

...nefits of a configurationless O/R mapper - ActiveRecord. I can hack a of this together in PHP, or configure it up with Hibernate, but with AR, I''m good to go, out of the box, for the basics - and the advanced requires just a few lines. 3. I also enjoy the fact that ActionPack does the bookkeeping necessary to turn URLs into Controller+Action+Template, and (using url_for), vice versa. Also that it prepops forms, and creates objects from form data. 4. Last, I find the rails command line and environment to be very convienent. I''m referring to the Rails::Generator and Rails::Ini...

Hello, I've been trying to make an old (about -95) small program for bookkeeping to run under wine. I managed now to install it with ddeml.dll set to native, but when I try to run it, following messages appear ~/.wine/drive_c/WKP> wine WKP.EXE err:ddeml:WDML_CreateString Unknown code page 850 wine: Unhandled exception 0xc0000090 at address 0x13df:0x00000f52 (thread 000c),...

When adding / removing an existing user to / from an existing group, is there anything more to it than bookkeeping the 'member' and 'memberOf' attributes of the respective entries? I'm currently writing a small tool to maintain POSIX attributes in AD and it seems that membership could be changed without falling back to samba-tool. When it's done and tested I'll be glad to share...

...t; Granted, LLVM currently doesn't really do much of this, but the > infastructure is there to do so. Right, but you can get this by doing profile directed optimisation during development so end users/production systems don't have the overhead. Also it seems to me that at some point the bookkeeping and analysis overhead for these optimisations would reduce performance of the program by more than they improve it. Eg keeping track of which calls are candidates for inlining may increase memory usage, so increasing swapping or decreasing cache utilisation, so losing you more performance than it g...

The NBD spec requires that a server doing structured reads must not succeed unless it covers the entire buffer with reply chunks. In the general case, this requires a lot of bookkeeping to check whether offsets were non-overlapping and sufficient, and we'd rather defer such checking to an optional callback function. But a callback function will only be reached per chunk, while we still want to fail the overall read if the callback function was never called because the server e...

...consists only of METADATA_KIND records. The latter is used only in the METADATA_ATTACHMENT block within function blocks (for metadata attached to instructions). For ThinLTO we want to delay the parsing of module level metadata until all functions have been imported from that module (there is some bookkeeping used to suture it up when we read it during a post-pass). However, I do need the METADATA_KIND records since that is used when parsing the function body being imported. In my ThinLTO prototype I was simply skipping the first METADATA_BLOCK and always parsing the second, since I knew from inspecting...